Re: passing device parameters to driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/31/06, Jan Hudec <bulb@xxxxxx> wrote:
>
> Have you ever seen kernel build system?

I have indeed.

> However, the above option should NOT be compile-time. Either implement
> appropriate IOCTL so it can be set by ifconfig,
> --
>                                                  Jan 'Bulb' Hudec <bulb@xxxxxx>

Ok it's clear now for me that the mac address should not be passed
this way. For the PHY layer address though, I still think its
necessary.

I couldn't describe my intention very well. My intention was that the
parameter shouldn't be present in the driver but rather discovered
during driver/device matching. The irq number is an example. The
rationale is that it's defined on the device's side, and the driver
finds out about it by probing, either examining the device itself or
the device structure declared at compile time. So defines may not help
there, it seems I need some data accessible from the device structure,
and platform_data looks like a suitable field for this.

I think I should look at the source perhaps there would be examples of
this kind for arbitrary device parameters.

Thanks,
Bahadir

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux