On Wed, Nov 16, 2005 at 04:57:11PM -0500, Tyler Trafford wrote: > On Wed, Nov 16, 2005 at 04:27:28PM -0500, Axel Thimm wrote: > > On Wed, Nov 16, 2005 at 03:10:42PM -0600, Adam Forsyth wrote: > > > On 11/16/05, Hans Verkuil <[EMAIL PROTECTED]> wrote: > > > > I think we should put the old method of loading from /lib/modules back > > > > into ivtv-0.4.1. It's not that much code and it's not really in the > > > > way. Opinions? Just for the record: 0.5.x will only support the hotplug > > > > method. > > > > > > Jut a note from the other thread: having hotplug only will prevent > > > people from putting ivtv into their initrd images so they can use the > > > xdriver and graphical boot to get their boot messages on their TVs. > > > > I think that's a very important asset for the PVR industry. The ivtv > > based systems on PVR-250 (e.g. SageTV) like to get a framebuffer early > > to splash their Logo and some progress information. Home > > perfectionists will probably do the same, and some are abusing swsusp2 > > with fb splashing for "instanton" systems. > > The reccomended way of dealing with this sort of thing is to build the > firmware into the driver. The size involved in this case makes that > undesireable though. > > I think newer initramfs startup builders like mkinitramfs and yaird > include udev (which is totally replacing hotplug) in the image, which > may solve this.
It already replaces hotplug, e.g. on FC4 and RHEL4, but it only provides a minimum functionality to deal with some SCSI and FC hotplug events to allow for early device creation/presentation and multipathing. AFAIK it doesn't deal with firmwares, and isn't (currently) intended to do so. Even the udev functionality is so minimal that you don't even have udev rules/permissions. -- Axel.Thimm at ATrpms.net
pgpmtTJTc6k5y.pgp
Description: PGP signature
_______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
