Re: e2b2rom_init_one(): Unable to register resource

On Sun, Feb 18, 2007 at 07:49:34PM +0200, Dan Aloni wrote:
| > Making window->phys u32 seems like a cleaner fix.
| > (untested) 
| 
| With this fix it still looks somewhat broken:
| 

Actually, Dan, I even don't know to do :( May be Andi know...
I think the problem is 'cause pci_read_config_word returns 0x4
and window->phys remains on 0.

		Cyrill

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • e2b2rom_init_one(): Unable to register resource
    • From: Dan Aloni <[email protected]>
  • Re: e2b2rom_init_one(): Unable to register resource
    • From: Cyrill Gorcunov <[email protected]>
  • Re: e2b2rom_init_one(): Unable to register resource
    • From: Andi Kleen <[email protected]>
  • Re: e2b2rom_init_one(): Unable to register resource
    • From: Dan Aloni <[email protected]>

• Prev by Date: Re: PCI riser cards and PCI irq routing, etc
• Next by Date: Re: 2.6.20-mm2
• Previous by thread: Re: e2b2rom_init_one(): Unable to register resource
• Next by thread: Re: e2b2rom_init_one(): Unable to register resource
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]