On Wed, Apr 21, 2010 at 2:40 PM, Colin Walters <walters@xxxxxxxxxx> wrote: > On Wed, Apr 21, 2010 at 7:08 AM, Peter Robinson <pbrobinson@xxxxxxxxx> wrote: > >> >> I've spent a little time looking at the hardware side of things and >> done a basic patch for some of the hardware stuff based on the current >> rawhide comps file. I've broken it down into network/server/misc for >> the time being and pushed the print stuff over to its group. More can >> be done as it was a quick look through. The old hardware-support >> currently includes all the other groups so there's no real change for >> current builds overall. > > This looks like a good start. I think the way this kind of thing > should work in general is that the system detects if you have the > hardware, and dynamically installs support for it. We'd need some > database mapping things like USB ids to packages. Networking is an > exception; we should include as many drivers/tools for > networking-related functionality as possible so that the system can be > bootstrapped. Well basically the way I've done the first swipe above won't impact anything that just includes @hardware-support as it just includes all groups. Those that want to drop stuff can register specific groups. I was thinking of making hardware-support-network hardware-support-wireless but then realises there was a couple of DSL firmwares in the list. In most cases for a server this would make no difference as servers don't generally have wireless and if there is any wired server ethernet in there I would probably move it to server but I think they're all contained in linux-firmware anyway. > Basically: if you have a GPS chip, gypsy gets installed and runs. If > you don't, it doesn't. Agreed. But in the interim until we get pci/usb id matching I figured this would be a good start. Is it OK to push it to rawhide, are we too late in the process for F-13 given the default doesn't change any of the standard builds? Peter -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
