* Re: udev and ISA network cards
2009-06-26 10:42 udev and ISA network cards Olaf
@ 2009-06-26 11:15 ` Kay Sievers
2009-06-30 5:45 ` Olaf
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Kay Sievers @ 2009-06-26 11:15 UTC (permalink / raw)
To: linux-hotplug
On Fri, Jun 26, 2009 at 12:42, Olaf<mailinglists@ban-solms.de> wrote:
> I would like to use ISA cards in combination with persistent net rules,
> especially renaming ethX to something like internal / internet / etc. as
> this is somewhat easier to remember ;-)
>
> Is this at all possible?
It should work.
> KERNEL[1246007462.711276] add /devices/isa/3c509.0 (isa)
This is the card device.
> KERNEL[1246007462.713145] add /devices/virtual/net/eth0 (net)
This is the network interface device, which needs to be connected to
the card device as a parent.
Then it would look like:
/devices/isa/3c509.0/net/eth0
and only then the persistent rule generator will kick in.
This needs to be fixed in the kernel driver, it needs to set the
parent device of the netdev before it is registered.
Kay
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: udev and ISA network cards
2009-06-26 10:42 udev and ISA network cards Olaf
2009-06-26 11:15 ` Kay Sievers
@ 2009-06-30 5:45 ` Olaf
2009-06-30 6:20 ` Hannes Reinecke
2009-07-02 6:33 ` Olaf
3 siblings, 0 replies; 5+ messages in thread
From: Olaf @ 2009-06-30 5:45 UTC (permalink / raw)
To: linux-hotplug
Kay Sievers wrote:
>> I would like to use ISA cards in combination with persistent net rules,
>> especially renaming ethX to something like internal / internet / etc. as
>> this is somewhat easier to remember ;-)
>>
>> Is this at all possible?
>
> It should work.
[... snip snip ...]
> This needs to be fixed in the kernel driver, it needs to set the
> parent device of the netdev before it is registered.
I was afraid you were going to say something like that ...
Ah well, I'll start staring at kernel driver code then.
regards
Olaf
PS: I'd appreciate any hints, pushes, shoves etc. to get me in proper
direction.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: udev and ISA network cards
2009-06-26 10:42 udev and ISA network cards Olaf
2009-06-26 11:15 ` Kay Sievers
2009-06-30 5:45 ` Olaf
@ 2009-06-30 6:20 ` Hannes Reinecke
2009-07-02 6:33 ` Olaf
3 siblings, 0 replies; 5+ messages in thread
From: Hannes Reinecke @ 2009-06-30 6:20 UTC (permalink / raw)
To: linux-hotplug
Hi Olaf,
Olaf wrote:
> Kay Sievers wrote:
>
>>> I would like to use ISA cards in combination with persistent net rules,
>>> especially renaming ethX to something like internal / internet / etc. as
>>> this is somewhat easier to remember ;-)
>>>
>>> Is this at all possible?
>>
>> It should work.
>
> [... snip snip ...]
>
>> This needs to be fixed in the kernel driver, it needs to set the
>> parent device of the netdev before it is registered.
>
> I was afraid you were going to say something like that ...
> Ah well, I'll start staring at kernel driver code then.
>
Which would help you only to a very limited amount.
udev relies on device autodetection, ie a (hardware) device must
have some means by which someone else can identify it.
With PCI this is no problem at all, as each device has its
vendor/device ID as per spec.
ISA OTOH is a different beast. And if you trawl memory back to
the ISA days, the main problem with it was that it _doesn't_
have an independent identifier.
IIRC you couldn't even identify the slot itself; each device
mostly hardcoded to use a specific I/O address / region and
some IRQ. And it was up to the task of the admin to ensure
each device got a separate addr/irq tuple.
Hence they invented PnP IDs which provide for exactly this
sort of identifier.
So, translated to udev this means that any ISA card providing
PnP IDs should work, or at least it should be possible to make
it work with udev.
Any ISA card _not_ providing PnP IDs you're basically out of luck.
The only choice you'd have here is to use some sort of lookup-table
which provides a static assignment between IO addresses and drivers.
HTH.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: udev and ISA network cards
2009-06-26 10:42 udev and ISA network cards Olaf
` (2 preceding siblings ...)
2009-06-30 6:20 ` Hannes Reinecke
@ 2009-07-02 6:33 ` Olaf
3 siblings, 0 replies; 5+ messages in thread
From: Olaf @ 2009-07-02 6:33 UTC (permalink / raw)
To: linux-hotplug
Hi Hannes,
thanks for your thoughts!
> udev relies on device autodetection, ie a (hardware) device must
> have some means by which someone else can identify it.
> With PCI this is no problem at all, as each device has its
> vendor/device ID as per spec.
>
> ISA OTOH is a different beast. And if you trawl memory back to
> the ISA days, the main problem with it was that it _doesn't_
> have an independent identifier.
> IIRC you couldn't even identify the slot itself; each device
> mostly hardcoded to use a specific I/O address / region and
> some IRQ. And it was up to the task of the admin to ensure
> each device got a separate addr/irq tuple.
For ISA (and PCI, USB, etc.) I use an additional method and do not fully
rely on autodetection to work.
In my case I have some sort of network configuration file, which
includes kernel modules, option if so required (i.e. ISA port addresses,
IRQs etc.) and the things needed for if up.
My network init script uses this config file to modprobe first and then
configure each interface.
> Hence they invented PnP IDs which provide for exactly this
> sort of identifier.
>
> So, translated to udev this means that any ISA card providing
> PnP IDs should work, or at least it should be possible to make
> it work with udev.
> Any ISA card _not_ providing PnP IDs you're basically out of luck.
> The only choice you'd have here is to use some sort of lookup-table
> which provides a static assignment between IO addresses and drivers.
The only problem I face is the lack of autodetection, so the config file
needs to be filled more or less manually. But there is not much one can
do about that with ISA cards.
OK, I have one additional problem, and that is the udev net device
renaming which is (understandably) not working with ISA cards ;-)
thanks
Olaf
^ permalink raw reply [flat|nested] 5+ messages in thread