Re: ipw2100: firmware problem

James Ketrenos <[email protected]> writes:
>>
> We've been looking into whether the initrd can have the firmware affixed
> to the end w/ some magic bytes to identify it.  If it works, enhancing
> the request_firmware to support both hotplug and an initrd approach may
> be reasonable.

That space is already used in common distributions for replacement DSDTs

I guess at some point we will need a file system in there, but - oops -
we already have one, dont we? :)

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

---

• Follow-Ups:
  • Re: ipw2100: firmware problem
    • From: Olivier Galibert <[email protected]>

• References:
  • ipw2100: firmware problem
    • From: Pavel Machek <[email protected]>
  • Re: ipw2100: firmware problem
    • From: James Ketrenos <[email protected]>

• Prev by Date: Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
• Next by Date: Re: [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers - take 2
• Previous by thread: Re: ipw2100: firmware problem
• Next by thread: Re: ipw2100: firmware problem
• 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]