Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, Mar 09, 2005 at 08:19:42AM +0100, Dominik Brodowski wrote: > On Wed, Mar 09, 2005 at 04:45:09PM +1100, Benjamin Herrenschmidt wrote: > > On Wed, 2005-03-09 at 00:16 +0100, Dominik Brodowski wrote: > > > > Dominik Brodowski <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Most pcmcia devices

Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

> > > The difficulty is that extracting and evaluating them breaks the > > > wonderful > > > bus-independent MODNAME implementation for hotplug suggested by Roman > > > Kagan > > > ( http://article.gmane.org/gmane.linux.hotplug.devel/7039 ), and that > > > these > > > strings may contain

Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, Mar 09, 2005 at 04:45:09PM +1100, Benjamin Herrenschmidt wrote: > On Wed, 2005-03-09 at 00:16 +0100, Dominik Brodowski wrote: > > > Dominik Brodowski <[EMAIL PROTECTED]> wrote: > > > > > > > > Most pcmcia devices are matched to drivers using "product ID strings" > > > > embedded in the

Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, Mar 09, 2005 at 04:45:09PM +1100, Benjamin Herrenschmidt wrote: > On Wed, 2005-03-09 at 00:16 +0100, Dominik Brodowski wrote: > > > Dominik Brodowski <[EMAIL PROTECTED]> wrote: > > > > > > > > Most pcmcia devices are matched to drivers using "product ID strings" > > > > embedded in the

Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, 2005-03-09 at 00:16 +0100, Dominik Brodowski wrote: > > Dominik Brodowski <[EMAIL PROTECTED]> wrote: > > > > > > Most pcmcia devices are matched to drivers using "product ID strings" > > > embedded in the devices' Card Information Structures, as "manufactor ID / > > > card ID" matches

Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Tue, Mar 08, 2005 at 03:37:07PM -0800, Greg KH wrote: > module aliases, and fixing up modprobe to handle spaces in module > aliases wouldn't work out easier. spaces _and_ characters. And characters are already used to separate different fields. pcmcia:pa"some string"pb"some other string"

Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, Mar 09, 2005 at 12:16:36AM +0100, Dominik Brodowski wrote: > > Dominik Brodowski <[EMAIL PROTECTED]> wrote: > > > > > > Most pcmcia devices are matched to drivers using "product ID strings" > > > embedded in the devices' Card Information Structures, as "manufactor ID / > > > card ID"

Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, Mar 09, 2005 at 12:16:36AM +0100, Dominik Brodowski wrote: > > Dominik Brodowski <[EMAIL PROTECTED]> wrote: > > > > > > Most pcmcia devices are matched to drivers using "product ID strings" > > > embedded in the devices' Card Information Structures, as "manufactor ID / > > > card ID"

Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

> Dominik Brodowski <[EMAIL PROTECTED]> wrote: > > > > Most pcmcia devices are matched to drivers using "product ID strings" > > embedded in the devices' Card Information Structures, as "manufactor ID / > > card ID" matches are much less reliable. Unfortunately, these strings > > cannot > > be

Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Tue, 8 Mar 2005, Dominik Brodowski wrote: > >Unfortunately, these strings cannot > be passed to userspace for easy userspace-based loading of appropriate > modules (MODNAME -- hotplug), so my suggestion is to also store crc32 hashes > of the strings in the

Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

Dominik Brodowski <[EMAIL PROTECTED]> wrote: > > Most pcmcia devices are matched to drivers using "product ID strings" > embedded in the devices' Card Information Structures, as "manufactor ID / > card ID" matches are much less reliable. Unfortunately, these strings cannot > be passed to

PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

Andrew, Linus, all, [note: for detailed code please take a look at 2.6.11-mm2] Most pcmcia devices are matched to drivers using "product ID strings" embedded in the devices' Card Information Structures, as "manufactor ID / card ID" matches are much less reliable. Unfortunately, these strings

PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

Andrew, Linus, all, [note: for detailed code please take a look at 2.6.11-mm2] Most pcmcia devices are matched to drivers using product ID strings embedded in the devices' Card Information Structures, as manufactor ID / card ID matches are much less reliable. Unfortunately, these strings cannot

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

Dominik Brodowski [EMAIL PROTECTED] wrote: Most pcmcia devices are matched to drivers using product ID strings embedded in the devices' Card Information Structures, as manufactor ID / card ID matches are much less reliable. Unfortunately, these strings cannot be passed to userspace for

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Tue, 8 Mar 2005, Dominik Brodowski wrote: Unfortunately, these strings cannot be passed to userspace for easy userspace-based loading of appropriate modules (MODNAME -- hotplug), so my suggestion is to also store crc32 hashes of the strings in the

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

Dominik Brodowski [EMAIL PROTECTED] wrote: Most pcmcia devices are matched to drivers using product ID strings embedded in the devices' Card Information Structures, as manufactor ID / card ID matches are much less reliable. Unfortunately, these strings cannot be passed to

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, Mar 09, 2005 at 12:16:36AM +0100, Dominik Brodowski wrote: Dominik Brodowski [EMAIL PROTECTED] wrote: Most pcmcia devices are matched to drivers using product ID strings embedded in the devices' Card Information Structures, as manufactor ID / card ID matches are much less

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, Mar 09, 2005 at 12:16:36AM +0100, Dominik Brodowski wrote: Dominik Brodowski [EMAIL PROTECTED] wrote: Most pcmcia devices are matched to drivers using product ID strings embedded in the devices' Card Information Structures, as manufactor ID / card ID matches are much less

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Tue, Mar 08, 2005 at 03:37:07PM -0800, Greg KH wrote: module aliases, and fixing up modprobe to handle spaces in module aliases wouldn't work out easier. spaces _and_ characters. And characters are already used to separate different fields. pcmcia:pasome stringpbsome other string doesn't

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, 2005-03-09 at 00:16 +0100, Dominik Brodowski wrote: Dominik Brodowski [EMAIL PROTECTED] wrote: Most pcmcia devices are matched to drivers using product ID strings embedded in the devices' Card Information Structures, as manufactor ID / card ID matches are much less

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, Mar 09, 2005 at 04:45:09PM +1100, Benjamin Herrenschmidt wrote: On Wed, 2005-03-09 at 00:16 +0100, Dominik Brodowski wrote: Dominik Brodowski [EMAIL PROTECTED] wrote: Most pcmcia devices are matched to drivers using product ID strings embedded in the devices' Card

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, Mar 09, 2005 at 04:45:09PM +1100, Benjamin Herrenschmidt wrote: On Wed, 2005-03-09 at 00:16 +0100, Dominik Brodowski wrote: Dominik Brodowski [EMAIL PROTECTED] wrote: Most pcmcia devices are matched to drivers using product ID strings embedded in the devices' Card

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

The difficulty is that extracting and evaluating them breaks the wonderful bus-independent MODNAME implementation for hotplug suggested by Roman Kagan ( http://article.gmane.org/gmane.linux.hotplug.devel/7039 ), and that these strings may contain spaces and other strange

Re: PCMCIA product id strings - hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]

On Wed, Mar 09, 2005 at 08:19:42AM +0100, Dominik Brodowski wrote: On Wed, Mar 09, 2005 at 04:45:09PM +1100, Benjamin Herrenschmidt wrote: On Wed, 2005-03-09 at 00:16 +0100, Dominik Brodowski wrote: Dominik Brodowski [EMAIL PROTECTED] wrote: Most pcmcia devices are matched to