Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1691682
| From | David Laight <David.Laight@ACULAB.COM> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | RE: [PATCH 1/3] mfd: Add support for FTDI FT232H devices |
| Date | 2017-07-19 15:40 +0200 |
| Message-ID | <u4XmO-Lg-35@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <u1G8O-53s-33@gated-at.bofh.it> <u1Xjk-7kC-3@gated-at.bofh.it> <u2lEZ-5ZJ-3@gated-at.bofh.it> <u2lYl-6m0-9@gated-at.bofh.it> <u4Xd8-Hy-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
From: Anatolij Gustschin > Sent: 19 July 2017 14:30 ... > >Stupid question, I know, but I cannot help thinking: If you have an > >EEPROM then why the h... don't you use an application specific device > >ID? > > It would make sense for adapter devices that you can buy and plug. > In my particular case the configuration device with FTDI chips is > internal part of embedded board, the configuration interface is > never exposed to end users. I doesn't make sense to register an > ID for such hardware. Sounds like you should absolutely be registering an ID so that nothing can try to use it using the default one. David
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH 1/3] mfd: Add support for FTDI FT232H devices Anatolij Gustschin <agust@denx.de> - 2017-07-19 15:30 +0200
RE: [PATCH 1/3] mfd: Add support for FTDI FT232H devices David Laight <David.Laight@ACULAB.COM> - 2017-07-19 15:40 +0200
Re: [PATCH 1/3] mfd: Add support for FTDI FT232H devices Anatolij Gustschin <agust@denx.de> - 2017-07-19 17:10 +0200
csiph-web