On Wed, 2007-01-17 at 08:33 -0600, Mike McGrath wrote: > On 1/17/07, Christopher Blizzard <blizzard@xxxxxxxxxx> wrote: > > Elliot Lee wrote: > > > The biggest headache for me recently has seemed to be hardware support. > > > So far, to get my new storage server working half-decently, I've had to > > > recompile an lm_sensors chip driver with an experimental patch, and > > > download an experimental network driver that works very poorly. I think > > > in the past I underestimated the amount of pain people go through > > > getting their hardware to work. I wonder if there is interest in > > > creating a "Fedora Kernel" sub-project or something, to do things like: > > > - package up 3rd party drivers > > > - improve direct communications with driver developers > > > - create a distributed hardware test grid (participants would > > > download a nightly LiveCD image, boot it on a system with questionable > > > or untested hardware to automatically run a test suite, and report the > > > results back) > > > > Yep. I've basically been pushing for two big things: > > > > 1. Awesome hardware reporting. Including statistics on suspend/resume > > rates. I attended mjg59's talk today about supporting suspend + resume. > > It was pretty eye opening and I think there are some interesting > > things we could do there. > > I've got the hardware profiler (smolt) up and ready for review, we > should be able to add tons to it: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=222959 > > If you come up with a clever way of detecting suspend / resume issues > or successes let me know, we can get it in there. I'd assume it'd > would go something like "write file, suspend, resume delete file" "on > boot, look for written file, if it hasn't been deleted then the last > resume failed" ? > What's the relationship, if any, with the LHCP project also on hosted.fedoraproject.org? Compare: https://hosted.fedoraproject.org/projects/smolt with: https://hosted.fedoraproject.org/projects/LHCP Both seem to be attempting roughly the same task; though LHCP code seems to be purely client-side. LHCP has a way of "detecting" suspend/resume issues: it asks the user :-) Hope this helps Dave _______________________________________________ fedora-advisory-board mailing list fedora-advisory-board@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board _______________________________________________ fedora-advisory-board-readonly mailing list fedora-advisory-board-readonly@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board-readonly
