On Mon, Jan 26, 2004 at 11:42:42PM +0100, Gaudenz Steinlin wrote:
> I'm not really sure if it's worth the effort. I think we wuld better put
> our limited time into fixing the already reported discover1 issues and
> providing discover2 packages (I will work on the latter tomorrow).
That's fine wit
Am Mon, den 26.01.2004 schrieb David Nusinow um 23:56:
> On Mon, Jan 26, 2004 at 09:22:24PM +0100, Gaudenz Steinlin wrote:
> > Discover2 will have a general mechanism to avoid these name conflicts.
> > The hardware database has a field for the kernel version.
> >
> > Beside this (which technicall
On Mon, Jan 26, 2004 at 09:22:24PM +0100, Gaudenz Steinlin wrote:
> Discover2 will have a general mechanism to avoid these name conflicts.
> The hardware database has a field for the kernel version.
>
> Beside this (which technically has nothing to do with kernel 2.6) there
> is nothing I know o
On Mon, Jan 26, 2004 at 09:22:24PM +0100, Gaudenz Steinlin wrote:
> Beside this (which technically has nothing to do with kernel 2.6) there
> is nothing I know of which is better suited for 2.6 in discover2 as in
> discover1. By it's very design either discover1 nor discover2 should
> depend on
David Nusinow schrieb:
On Sun, Jan 25, 2004 at 09:28:33PM +0100, Harald Dunkel wrote:
2.6.1. For 2.4.22 its called "ehci-hcd", as it seems. You have
to enable the optional development drivers in menuconfig.
The naming conflicts between 2.4.x and 2.6.x is something that
should be addressed for di
On Sun, Jan 25, 2004 at 10:21:50PM +0100, Harald Dunkel wrote:
> What will be the final solution for Sarge: discover or discover2?
The plan right now is to use discover1 in the installer, and provide
discover2 as well for install later. discover2 may be its own package,
or it may be the discover p
David Nusinow wrote:
On Sun, Jan 25, 2004 at 09:28:33PM +0100, Harald Dunkel wrote:
2.6.1. For 2.4.22 its called "ehci-hcd", as it seems. You have
to enable the optional development drivers in menuconfig.
The naming conflicts between 2.4.x and 2.6.x is something that
should be addressed for discov
The naming conflicts between 2.4.x and 2.6.x is something that
should be addressed for discover-data. Would it be possible to
provide a second pci database for the 2.6.x kernels? Or does
discover2 provide a smarter solution?
The kernel (or are it the modutils?) do. In 2.6, a dash in a module name
On Sun, Jan 25, 2004 at 09:28:33PM +0100, Harald Dunkel wrote:
> 2.6.1. For 2.4.22 its called "ehci-hcd", as it seems. You have
> to enable the optional development drivers in menuconfig.
>
> The naming conflicts between 2.4.x and 2.6.x is something that
> should be addressed for discover-data. Wo
On Sun, Jan 25, 2004 at 09:28:33PM +0100, Harald Dunkel wrote:
> Petter Reinholdtsen wrote:
> >[Harald Dunkel]
> >
> >>+ 11063104usb ehci_hcdUSB 2.0
> >
> >
> >Which kernel version is this? It is not present in my 2.4.22 kernel.
> >
>
> 2.6.1. For 2.4.22 its called "ehci
Petter Reinholdtsen wrote:
[Harald Dunkel]
+ 11063104usb ehci_hcdUSB 2.0
Which kernel version is this? It is not present in my 2.4.22 kernel.
2.6.1. For 2.4.22 its called "ehci-hcd", as it seems. You have
to enable the optional development drivers in menuconfig.
The n
[Harald Dunkel]
> + 11063104usb ehci_hcdUSB 2.0
Which kernel version is this? It is not present in my 2.4.22 kernel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sun, 25 Jan 2004 10:22:46 +0100, Harald Dunkel
<[EMAIL PROTECTED]> wrote:
Are there some *.deb files available for discover2?
Go to http://platform.progeny.com/discover/ and click on mailing lists.
There is some info on that in there.
--
Matthew A. Nicholson
Matt-Land.com
--
To UNSUBSCRIB
Hi folks,
Please excuse the wide distribution, but I am not sure who owns
the PCI database for discover.
Something for pci.lst:
# (lspci; lspci -n) | grep 00:09.2
00:09.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
00:09.2 Class 0c03: 1106:3104 (rev 51)
Here is the (obvious) patch
14 matches
Mail list logo
