--Kj7319i9nmIyA2yE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Christopher Schultz <christopher.d.schultz@comcast.net> [2004-01-08 03:24=
:04]:
> >>Is USB support a matter of pulling in=20
> >>configuration parameters from one of the other files (e.g.,=20
> >>arch/i386/GENERIC), or is there something funky about the Qube that=20
> >>prevents the use of a USB card?
> >
> >In theory it should go plain road...
>=20
> I've always been intrigued by this message in my dmesg:
>=20
> 	VIA Technologies VT83C572 USB Controller (USB serial bus,
> 	revision 0x02) at pci0 dev 9 function 2 not configured
>=20
> I also got this when I used to have the original Linux installed:
>=20
> $ cat /proc/pci
>=20
>   Bus  0, device   9, function  2:
>     USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 2).
>       Medium devsel.  Master Capable.  Latency=3D22.
>       I/O at 0x300.
>=20
> Anyone know anything about this? I'd love to hack the hardware if it=20
> wouldn't be too damaging.

It's the 82C586 'southbridge' chip which provides the IDE for the Qube
also contains amongst other things, a USB host controller in the same
package, so it's getting detected.

Without looking, I suspect the necessary pins on the package aren't
connected anywhere, but I don't know how much extra electronics goo has
to be put in place in between the chip and the USB port to know if it's
feasible or not.

Matt
--=20
"I've seen his style before, terminal psychotic!"

--Kj7319i9nmIyA2yE
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (NetBSD)

iD8DBQE//RqHKP58eR+X2TMRAnpcAJoDvODqB0HXG8vXK7L9efk1lTa13gCfQ7sU
0IK+LkoCSu0vZfOuartUx6Q=
=lAMt
-----END PGP SIGNATURE-----

--Kj7319i9nmIyA2yE--