Date: Thu, 8 Jul 2010 14:46:16 -0700 From: Freddie Cash <fjwcash@gmail.com> To: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: 8.x grudges Message-ID: <AANLkTimYyuBJiXl0pWQGoKA1Tp1memgh0Fnk1MYprbt-@mail.gmail.com> In-Reply-To: <4C3644D1.6000407@foolishgames.com> References: <4C34C5DE.7040007@aldan.algebra.com> <20100708210611.GA34250@server.vk2pj.dyndns.org> <4C3644D1.6000407@foolishgames.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 8, 2010 at 2:36 PM, Lucas Holt <luke@foolishgames.com> wrote: > On 07/08/10 17:06, Peter Jeremy wrote: >> >> On 2010-Jul-07 14:22:22 -0400, "Mikhail T."<mi+thun@aldan.algebra.com> >> =C2=A0wrote: >> >>> >>> In no particular order: >>> >>> =C2=A0 1. >>> =C2=A0 =C2=A0 =C2=A0A picture, that one of the systems was displaying a= t boot (and >>> =C2=A0 =C2=A0 =C2=A0then used as a screen-saver), =C2=A0stopped showing= properly. The >>> =C2=A0 =C2=A0 =C2=A0colors are right, but the picture is distorted beyo= nd recognition. >>> =C2=A0 =C2=A0 =C2=A0The relevant part of loader.conf is: >>> >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0splash_pcx_load=3D"YES" >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0vesa_load=3D"YES" >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bitmap_load=3D"YES" >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bitmap_name=3D"/boot/187426-9-quokka-= dreaming.pcx" >>> >> >> It's a bit difficult to provide any useful input without some idea >> of what the picture should and does look like. =C2=A0Can you please post >> the actual bitmap as well as a picture of your screen showing the >> problem. >> >> >>> >>> =C2=A0 3. >>> =C2=A0 =C2=A0 =C2=A0Likewise, having "device ugen" breaks config(8) -- = another >>> =C2=A0 =C2=A0 =C2=A0undocumented incompatibility. >>> >> >> Can you please advise where it is documented that "device ugen" >> is valid in a FreeBSD-8 config file? >> > NAME > =C2=A0 =C2=A0 ugen -- USB generic device support > > SYNOPSIS > =C2=A0 =C2=A0 To compile this driver into the kernel, place the following= line in your > =C2=A0 =C2=A0 kernel configuration file: > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 device ugen > > =C2=A0 =C2=A0 Alternatively, to load the driver as a module at boot time,= place the > =C2=A0 =C2=A0 following line in loader.conf(5): > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ugen_load=3D"YES" > > DESCRIPTION > =C2=A0 =C2=A0 The ugen driver provides support for all USB devices that d= o not have a > =C2=A0 =C2=A0 special driver. =C2=A0It supports access to all parts of th= e device, but not > =C2=A0 =C2=A0 in a way that is as convenient as a special purpose driver. > > =C2=A0 =C2=A0 There can be up to 127 USB devices connected to a USB bus. = =C2=A0Each USB > =C2=A0 =C2=A0 device can have up to 16 endpoints. =C2=A0Each of these end= points will commu- > <snip> > > uname -a > FreeBSD lholt-desktop.primemediaanalysis.com 8.0-RELEASE-p3 FreeBSD > 8.0-RELEASE-p3 #0: Tue May 25 20:54:11 UTC 2010 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC =C2=A0amd= 64 > > I'm not going to argue in favor of any points in this rant, but it is in = the > man page. Looks like you found a bug. :) ugen is not listed in any of the NOTES files, and is not a valid device entry for a 8.x kernel config file. Maybe that man page got skipped in the USB stack upgrade? Should definitely add a PR for this man page to be updated for the new USB stack. Maybe even do an audit of the rest of the USB devices to make sure the man pages for those are correct as well. --=20 Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimYyuBJiXl0pWQGoKA1Tp1memgh0Fnk1MYprbt->