> > Why are you so fixated on special-casing the single character '/'?Why are you thinking of it as namespaces then? It isn't. The "firmware key" lives in a flat namespace where each key is an arbitrary nul-terminated string. No, it doesn't. There's no need to think of it that way. Look at a uevent now: UEVENT[1211722721.323011] add /devices/pci0001:10/0001:10:12.0/ssb0:0/= firmware/ssb0:0 (firmware) ACTION=3Dadd DEVPATH=3D/devices/pci0001:10/0001:10:12.0/ssb0:0/firmware/ssb0:0 SUBSYSTEM=3Dfirmware FIRMWARE=3Db43/b0g0bsinitvals5.fw TIMEOUT=3D60 SEQNUM=3D1376 The "firmware key" is contained in the FIRMWARE environment variable. If you want to allow loading multiple firmwares at the same time, you wouldn't have to make the key part of the device name, you would only have to add a unique ID to the firmware device name, say =EF=BB=BF UEVENT[1211722721.323011] add /devices/pci0001:10/0001:10:12.0/ssb0:0/= firmware/ssb0:0-1234 (firmware) ACTION=3Dadd DEVPATH=3D/devices/pci0001:10/0001:10:12.0/ssb0:0/firmware/ssb0:0-1234 SUBSYSTEM=3Dfirmware FIRMWARE=3Db43/b0g0bsinitvals5.fw TIMEOUT=3D60 SEQNUM=3D1376 johannes
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Kok, Auke | Re: Linux 2.6.21-rc1 |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jeff Garzik | Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Eric Dumazet | [PATCH] net: remove superfluous call to synchronize_net() |
