-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/15/07 11:46, Greg Folkert wrote:
> On Mon, 2007-01-15 at 09:33 -0600, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 01/14/07 23:58, Greg Folkert wrote:
>>> On Sat, 2007-01-13 at 11:43 -0800, Paul Johnson wrote:
>
On Mon, 2007-01-15 at 09:33 -0600, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 01/14/07 23:58, Greg Folkert wrote:
> > On Sat, 2007-01-13 at 11:43 -0800, Paul Johnson wrote:
> >> Greg Folkert wrote:
> >>
> >>> On Fri, 2007-01-12 at 22:01 -0500, Grok Mogger wrote:
>
On Monday 15 January 2007 09:33, Ron Johnson wrote:
> On 01/14/07 23:58, Greg Folkert wrote:
> > On Sat, 2007-01-13 at 11:43 -0800, Paul Johnson wrote:
> >> Greg Folkert wrote:
> >>> On Fri, 2007-01-12 at 22:01 -0500, Grok Mogger wrote:
> [EMAIL PROTECTED] wrote:
> "The kernel comes with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/14/07 23:58, Greg Folkert wrote:
> On Sat, 2007-01-13 at 11:43 -0800, Paul Johnson wrote:
>> Greg Folkert wrote:
>>
>>> On Fri, 2007-01-12 at 22:01 -0500, Grok Mogger wrote:
[EMAIL PROTECTED] wrote:
"The kernel comes with it's own docum
On Sat, 2007-01-13 at 11:43 -0800, Paul Johnson wrote:
> Greg Folkert wrote:
>
> > On Fri, 2007-01-12 at 22:01 -0500, Grok Mogger wrote:
> >> [EMAIL PROTECTED] wrote:
> >
> >>
> >> "The kernel comes with it's own documentation section. Some
> >> good reading there."
> >>
> >> Sounds great. Wh
On Fri, Jan 12, 2007 at 10:50:19PM -0500, Grok Mogger wrote:
> My goal is ultimately the following. I want to be able to say
> "I'm interested in getting a Super Device 4000" and then go
> through whatever steps I need to verify that it will or won't
> work before I even try it. I'd like to
on Sat, Jan 13, 2007 at 05:46:04PM -0500 Grok Mogger mumbled:
> This sounds like if I know for a fact that the device I'm
> interested in uses "Chipset Awesome 100c", then I could start
> grep'ing through the kernel source for parts and permutations of
> the chipset name hoping to find some ma
Andrei Popescu wrote:
On Fri, 12 Jan 2007 22:50:19 -0500
Grok Mogger <[EMAIL PROTECTED]> wrote:
Is it safe to say that drivers are really for a chipset, not a
device? And so therefore, support for a device really boils
down to "is the chipset supported?" not "is the device supported"?
Yes,
Kevin Ross wrote:
Here's a code snippet from ne2k-pci.c, the NE2000-clone NIC driver:
static struct {
char *name;
int flags;
} pci_clone_list[] __devinitdata = {
{"RealTek RTL-8029", REALTEK_FDX},
{"Winbond 89C940", 0},
{"Compex RL2000", 0},
{"KTI ET32P2", 0},
{"NetVin NV5000SC", 0},
{
Kevin Mark writes:
>>
wizbang 1000 (chipset A) uses kernel module P
wizbang 1000 (rev. 2, chipset B) uses kernel Q.
> John Hasler wrote:
They also sometimes have the chips labeled with their own labels so that
somebody has to do some reverse engineering to find out what is really in
there.
On Fri, Jan 12, 2007 at 08:14:58PM -0800, Kevin Ross wrote:
>
> Having a comprehensive list of supported chipsets would be useful, though.
> If
> some text-parsing wizard out there would like to write such a program, it
> would
> be interesting.
now if only manufacturers would put the chips
Grok Mogger <[EMAIL PROTECTED]> writes:
> "The kernel comes with it's own documentation section. Some good
> reading there."
>
> Sounds great. Where can I find that? =P
# aptitude install linux-doc-
where is the version of your kernel. The package might have
been called kernel-doc- in sarge
Greg Folkert wrote:
> On Fri, 2007-01-12 at 22:01 -0500, Grok Mogger wrote:
>> [EMAIL PROTECTED] wrote:
>
>>
>> "The kernel comes with it's own documentation section. Some
>> good reading there."
>>
>> Sounds great. Where can I find that? =P
>
> http://www.kernel.org/pub/linux/kernel/v2.6/l
Grok Mogger <[EMAIL PROTECTED]> writes:
> Thanks to everyone who's taken the time to respond. It's helped a
> lot. I'd still like some more help though if you can spare it. =)
Hear! Hear!
This has been really informative.
--
Hugh Lawson
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAI
On Fri, 12 Jan 2007 20:47:05 -0500
Grok Mogger <[EMAIL PROTECTED]> wrote:
> Hey everyone,
>
> If the default kernel that comes with Debian has all these built
> in drivers and modules, then shouldn't there be some way to just
> get a list of every supported device?
What about generic drivers l
On Fri, 12 Jan 2007 22:50:19 -0500
Grok Mogger <[EMAIL PROTECTED]> wrote:
> Is it safe to say that drivers are really for a chipset, not a
> device? And so therefore, support for a device really boils
> down to "is the chipset supported?" not "is the device supported"?
Yes, but not 100%. Along
Roberto C. Sanchez wrote:
> Some of the truly annoying problems crop up when you have
> BarWidget 175t manufactured before some date using chipsets from company
> C and BarWidget 175t manufactured after a certain date using chipsets
> from company D, but there is no change in model number.
Users
Here's a code snippet from ne2k-pci.c, the NE2000-clone NIC driver:
static struct {
char *name;
int flags;
} pci_clone_list[] __devinitdata = {
{"RealTek RTL-8029", REALTEK_FDX},
{"Winbond 89C940", 0},
{"Compex RL2000", 0},
{"KTI ET32P2", 0},
{"NetVin NV5000SC", 0},
{"Via 86C926", ONLY_16
Grok Mogger writes:
> Is it safe to say that drivers are really for a chipset, not a device?
> And so therefore, support for a device really boils down to "is the
> chipset supported?" not "is the device supported"?
Fairly safe.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wit
sdpatt2 wrote
> The kernel comes with it's own documentation section. Some good reading
> there.
Grok Mogger writes:
> Sounds great. Where can I find that?
Install the kernel source package for your kernel and look in
/usr/src/linux/Documentation.
--
John Hasler
--
To UNSUBSCRIBE, email to
Thanks to everyone who's taken the time to respond. It's helped
a lot. I'd still like some more help though if you can spare
it. =)
My goal is ultimately the following. I want to be able to say
"I'm interested in getting a Super Device 4000" and then go
through whatever steps I need to ve
On Fri, 2007-01-12 at 22:01 -0500, Grok Mogger wrote:
> [EMAIL PROTECTED] wrote:
>
> "The kernel comes with it's own documentation section. Some
> good reading there."
>
> Sounds great. Where can I find that? =P
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.19.tar.gz
Extract it and
[EMAIL PROTECTED] wrote:
on Fri, Jan 12, 2007 at 08:47:05PM -0500 Grok Mogger mumbled:
Hey everyone,
If I want to buy a new piece of hardware, and I want to figure
out if it's supported or not (BEFORE I buy it),
One good way is to take a knoppix disk to the 'puter store and boot
the shiny
Kevin Mark writes:
> wizbang 1000 (chipset A) uses kernel module P
> wizbang 1000 (rev. 2, chipset B) uses kernel Q.
They don't even always bother with changing the revision number. Sometimes
they just slipstream the change so that all units after a certain serial
number use the new chipset.
The
On Fri, Jan 12, 2007 at 08:47:05PM -0500, Grok Mogger wrote:
> Hey everyone,
>
> If the default kernel that comes with Debian has all these built
> in drivers and modules, then shouldn't there be some way to just
> get a list of every supported device?
>
> If I want to buy a new piece of hardwa
on Fri, Jan 12, 2007 at 08:47:05PM -0500 Grok Mogger mumbled:
> Hey everyone,
>
> If I want to buy a new piece of hardware, and I want to figure
> out if it's supported or not (BEFORE I buy it),
One good way is to take a knoppix disk to the 'puter store and boot
the shiny new machine off it.
On Fri, Jan 12, 2007 at 08:47:05PM -0500, Grok Mogger wrote:
> Hey everyone,
>
> If the default kernel that comes with Debian has all these built
> in drivers and modules, then shouldn't there be some way to just
> get a list of every supported device?
>
Nope. However, with enough work, you ca
Hey everyone,
If the default kernel that comes with Debian has all these built
in drivers and modules, then shouldn't there be some way to just
get a list of every supported device?
If I want to buy a new piece of hardware, and I want to figure
out if it's supported or not (BEFORE I buy it),
28 matches
Mail list logo
