Re: few questions on 'struct net_device'

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

 



On 2/1/07, Roman Mashak <mrv@xxxxxxxxxxxxx> wrote:
Hello, Rajat!
You wrote to "Roman Mashak" <mrv@xxxxxxxxxxxxx> on Wed, 31 Jan 2007 13:30:32
+0530:

 RJ> Yes you are right about the firware. Lets talk about IRQ. The firmware
 RJ> only finds out which irq lines a device can use and sets in its config
 RJ> space, an IRQ number that this device will use i.e. the IRQ that the
 RJ> device should generate when it wants to interrupt the CPU.

Thank you very much, it's much clear now. I have one more question about the
other hardware relevant fields in 'struct net_device': 'base_addr' and
'[r]mem_start/end'. Why is 'base_addr' recommended to be assigned during
device probe, and not later when we can be sure we do need this resource?

And I didn't notice '8139too' driver uses '[r]mem_start', '[r]mem_end',
isn't it mandatory?

I don't have much idea about net_device, but the fields that you are
referring to are quite obsolete, I think. And hence not much drivers
use them today.

Regards,

Rajat

--
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