On Tue, Jan 30, 2007 at 05:23:44PM -0500, Lennart Sorensen wrote:
> On Tue, Jan 30, 2007 at 05:12:31PM -0500, Jeff Garzik wrote:
> > You mean the bcm43xx wireless driver that's been upstream for months?
>
> And seems to do 802.11b only and screw up the eeprom settings so that
> the windows driver
On 01/02/07, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
On 31 Jan 2007 11:08:14 +0100, Andi Kleen <[EMAIL PROTECTED]> wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
> >
> > What? Throw a fresh-faced newbie instantly into the tar-pit of despair
> > that floppy.c is? Do you want everyone
On 31 Jan 2007 11:08:14 +0100, Andi Kleen <[EMAIL PROTECTED]> wrote:
Greg KH <[EMAIL PROTECTED]> writes:
>
> What? Throw a fresh-faced newbie instantly into the tar-pit of despair
> that floppy.c is? Do you want everyone just to run screaming from
> kernel development never to be seen again?
On Jan 31 2007 18:59, Lee Revell wrote:
> On 1/31/07, Theodore Tso <[EMAIL PROTECTED]> wrote:
>>
>> More specifically, Dave said that it "seemed rude" to just take the
>> driver and send updates, but maybe the best way of dealing with
>> out-of-tree drivers like lirc is to treat the out-of-tree
Lee Revell wrote:
On 1/31/07, Mark Lord <[EMAIL PROTECTED]> wrote:
I believe a BIG reason why lots of open-source drivers are out-of-tree
right now, is because lkml is perceived as being wayy too fussy
and petty about 80-column lines, brackets, etc.. for new code.
It's just not worth the
On 2/1/07, Nicolas Mailhot <[EMAIL PROTECTED]> wrote:
Not all of them.
It seems it's kosher to rewrite a corp GPL driver but not a "community" one.
As I said, Greg didn't say it was rude to write a new driver without consulting
the author of an existing driver.. corp *or* community.. so who
Le Jeu 1 février 2007 10:03, Trent Waddington a écrit :
> On 2/1/07, Nicolas Mailhot <[EMAIL PROTECTED]> wrote:
>> Well, reengineering nvidia/ati DRM is rude to ati/nvidia, so was
>> creating
>> tigon3, so was rewriting from scratch the GPL drivers some ATA vendors
>> published in the past, so
On 2/1/07, Nicolas Mailhot <[EMAIL PROTECTED]> wrote:
Well, reengineering nvidia/ati DRM is rude to ati/nvidia, so was creating
tigon3, so was rewriting from scratch the GPL drivers some ATA vendors
published in the past, so was spurning the SATA/SAS stack adaptec
offered...
It is rude, but
Le Jeu 1 février 2007 00:44, Greg KH a écrit :
> On Wed, Jan 31, 2007 at 06:00:15PM -0500, Theodore Tso wrote:
>> More specifically, Dave said that it "seemed rude" to just take the
>> driver and send updates, but maybe the best way of dealing with
>> out-of-tree drivers like lirc is to treat
Le Jeu 1 février 2007 00:44, Greg KH a écrit :
On Wed, Jan 31, 2007 at 06:00:15PM -0500, Theodore Tso wrote:
More specifically, Dave said that it seemed rude to just take the
driver and send updates, but maybe the best way of dealing with
out-of-tree drivers like lirc is to treat the
On 2/1/07, Nicolas Mailhot [EMAIL PROTECTED] wrote:
Well, reengineering nvidia/ati DRM is rude to ati/nvidia, so was creating
tigon3, so was rewriting from scratch the GPL drivers some ATA vendors
published in the past, so was spurning the SATA/SAS stack adaptec
offered...
It is rude, but
Le Jeu 1 février 2007 10:03, Trent Waddington a écrit :
On 2/1/07, Nicolas Mailhot [EMAIL PROTECTED] wrote:
Well, reengineering nvidia/ati DRM is rude to ati/nvidia, so was
creating
tigon3, so was rewriting from scratch the GPL drivers some ATA vendors
published in the past, so was spurning
On 2/1/07, Nicolas Mailhot [EMAIL PROTECTED] wrote:
Not all of them.
It seems it's kosher to rewrite a corp GPL driver but not a community one.
As I said, Greg didn't say it was rude to write a new driver without consulting
the author of an existing driver.. corp *or* community.. so who said
Lee Revell wrote:
On 1/31/07, Mark Lord [EMAIL PROTECTED] wrote:
I believe a BIG reason why lots of open-source drivers are out-of-tree
right now, is because lkml is perceived as being wayy too fussy
and petty about 80-column lines, brackets, etc.. for new code.
It's just not worth the
On Jan 31 2007 18:59, Lee Revell wrote:
On 1/31/07, Theodore Tso [EMAIL PROTECTED] wrote:
More specifically, Dave said that it seemed rude to just take the
driver and send updates, but maybe the best way of dealing with
out-of-tree drivers like lirc is to treat the out-of-tree drivers as a
On 31 Jan 2007 11:08:14 +0100, Andi Kleen [EMAIL PROTECTED] wrote:
Greg KH [EMAIL PROTECTED] writes:
What? Throw a fresh-faced newbie instantly into the tar-pit of despair
that floppy.c is? Do you want everyone just to run screaming from
kernel development never to be seen again?
On 01/02/07, Bartlomiej Zolnierkiewicz [EMAIL PROTECTED] wrote:
On 31 Jan 2007 11:08:14 +0100, Andi Kleen [EMAIL PROTECTED] wrote:
Greg KH [EMAIL PROTECTED] writes:
What? Throw a fresh-faced newbie instantly into the tar-pit of despair
that floppy.c is? Do you want everyone just to run
On Tue, Jan 30, 2007 at 05:23:44PM -0500, Lennart Sorensen wrote:
On Tue, Jan 30, 2007 at 05:12:31PM -0500, Jeff Garzik wrote:
You mean the bcm43xx wireless driver that's been upstream for months?
And seems to do 802.11b only and screw up the eeprom settings so that
the windows driver gets
Greg KH [EMAIL PROTECTED] writes:
On Wed, Jan 31, 2007 at 08:41:03PM +0300, Sergei Organov wrote:
Greg KH [EMAIL PROTECTED] writes:
[...]
And there are plenty of documented devices that no one cares enough
about to submit a driver for.
Any specific examples? I have a long list of
3. Vendor driver is rather close to the generic one being in the kernel,
so maybe it's better to improve generic one instead of adding yet
another driver to the tree.
Firstly can you post a patch which adds the relevant identifiers to the
current pcmcia serial driver so that 115,200
On Thu, Feb 01, 2007 at 02:59:03PM +0100, Erik Mouw wrote:
I can't remember that kind of corruption ever being reported to the
bcm43xx-dev mailing list.
Well I assumed it messed up the eeprom settings, since we had to go into
the advanced driver settings and change it from 802.11b only back to
On Tuesday 30 January 2007 23:23, Lennart Sorensen wrote:
On Tue, Jan 30, 2007 at 05:12:31PM -0500, Jeff Garzik wrote:
You mean the bcm43xx wireless driver that's been upstream for months?
And seems to do 802.11b only and screw up the eeprom settings so that
the windows driver gets confused
On Thu, Feb 01, 2007 at 04:46:38PM +0100, Michael Buesch wrote:
Nah, why do you think it will screw up the eeprom?
Did you try to completely power off the machine before rebooting
into windows?
No at the time I don't think I powered it off, and I suspect that is
probably what went wrong. The
On Thu, Feb 01, 2007 at 02:12:22PM +0100, Bartlomiej Zolnierkiewicz wrote:
On 31 Jan 2007 11:08:14 +0100, Andi Kleen [EMAIL PROTECTED] wrote:
Greg KH [EMAIL PROTECTED] writes:
What? Throw a fresh-faced newbie instantly into the tar-pit of despair
that floppy.c is? Do you want everyone
Alan [EMAIL PROTECTED] writes:
3. Vendor driver is rather close to the generic one being in the kernel,
so maybe it's better to improve generic one instead of adding yet
another driver to the tree.
Firstly can you post a patch which adds the relevant identifiers to the
current pcmcia
On 2/1/07, Lennart Sorensen [EMAIL PROTECTED] wrote:
Sometimes I might be. At least on the days I have to deal with problems
in Windows (it's not even my machine, so I don't get to pick what it
runs all the time. :) I haven't had particularly much luck getting a
stable wireless going on linux
On Thu, Feb 01, 2007 at 09:45:06AM -0500, Lennart Sorensen wrote:
On Thu, Feb 01, 2007 at 02:59:03PM +0100, Erik Mouw wrote:
I can't remember that kind of corruption ever being reported to the
bcm43xx-dev mailing list.
Well I assumed it messed up the eeprom settings, since we had to go
On Wed, 31 Jan 2007 21:20:06 +0100 Greg KH wrote:
On Wed, Jan 31, 2007 at 02:06:32PM +0100, Nicolas Mailhot wrote:
I'd really love if the same offer was extended to GPL out-of-tree
driver trees.
This kind of offer has _always_ been there for out-of-tree GPL
drivers. I have contacted many
On Wed, Jan 31, 2007 at 01:37:58PM -0500, Bob Copeland wrote:
> >Putting the "codingstyle" control aside, often it's because things look
> >too hackish.
>
> Also sometimes the authors know it's hackish, or just don't expect it
> to be generally useful to the world. I happen to own an out-of-tree
On Wed, Jan 31, 2007 at 10:15:20PM +0100, Nicolas Mailhot wrote:
> Le mercredi 31 janvier 2007 ?? 12:12 -0800, Greg KH a ??crit :
> > On Wed, Jan 31, 2007 at 02:06:32PM +0100, Nicolas Mailhot wrote:
>
> [Reordering for the sake of argument]
>
> > > There are many out-of-tree drivers (ivtv, lirc,
On Wed, Jan 31, 2007 at 08:41:03PM +0300, Sergei Organov wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
> [...]
> >> And there are plenty of documented devices that no one cares enough
> >> about to submit a driver for.
> >
> > Any specific examples? I have a long list of people who wish to write
>
On Thu, Feb 01, 2007 at 10:07:53AM +1000, Trent Waddington wrote:
> On 2/1/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >No, I'm going by Linus's rule here, if a person doesn't want their code
> >in the kernel tree, then I'm not going to forcefully put it there.
> >That's just being rude.
>
> Makes
On 1/31/07, Mark Lord <[EMAIL PROTECTED]> wrote:
Randy Dunlap wrote:
> On Wed, 31 Jan 2007 18:00:15 -0500 Theodore Tso wrote:
..
>> More specifically, Dave said that it "seemed rude" to just take the
>> driver and send updates, but maybe the best way of dealing with
>> out-of-tree drivers like
Randy Dunlap wrote:
On Wed, 31 Jan 2007 18:00:15 -0500 Theodore Tso wrote:
..
More specifically, Dave said that it "seemed rude" to just take the
driver and send updates, but maybe the best way of dealing with
out-of-tree drivers like lirc is to treat the out-of-tree drivers as a
kind of spec
On 2/1/07, Greg KH <[EMAIL PROTECTED]> wrote:
No, I'm going by Linus's rule here, if a person doesn't want their code
in the kernel tree, then I'm not going to forcefully put it there.
That's just being rude.
Makes sense when you put it that way. However, perhaps an offer to
take over the
On 1/31/07, Theodore Tso <[EMAIL PROTECTED]> wrote:
More specifically, Dave said that it "seemed rude" to just take the
driver and send updates, but maybe the best way of dealing with
out-of-tree drivers like lirc is to treat the out-of-tree drivers as a
kind of spec release, and just have
On Wed, Jan 31, 2007 at 06:00:15PM -0500, Theodore Tso wrote:
> On Wed, Jan 31, 2007 at 12:12:58PM -0800, Greg KH wrote:
> >
> > This kind of offer has _always_ been there for out-of-tree GPL drivers.
> > I have contacted many different groups and driver authors over the years
> > to offer my
On Wed, 31 Jan 2007 18:00:15 -0500 Theodore Tso wrote:
> On Wed, Jan 31, 2007 at 12:12:58PM -0800, Greg KH wrote:
> >
> > This kind of offer has _always_ been there for out-of-tree GPL drivers.
> > I have contacted many different groups and driver authors over the years
> > to offer my help in
On Wed, Jan 31, 2007 at 12:12:58PM -0800, Greg KH wrote:
>
> This kind of offer has _always_ been there for out-of-tree GPL drivers.
> I have contacted many different groups and driver authors over the years
> to offer my help in trying to get their code into the mainline kernel.
>
> Some take
On Wed, 31 Jan 2007 17:06:07 -0500 Dave Jones wrote:
> On Wed, Jan 31, 2007 at 12:12:58PM -0800, Greg Kroah-Hartman wrote:
>
> > > There are many out-of-tree drivers (ivtv, lirc, various webcam drivers,
> > > enhanced USB keyboard handlers...) with merging not planified or taking
> > > ages.
On Wed, Jan 31, 2007 at 12:12:58PM -0800, Greg Kroah-Hartman wrote:
> > There are many out-of-tree drivers (ivtv, lirc, various webcam drivers,
> > enhanced USB keyboard handlers...) with merging not planified or taking
> > ages.
>
> See my above comment about lirc. As for the others,
On Wed, 2007-01-31 22:56:03 +0100, Willy Tarreau <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 31, 2007 at 10:13:12PM +0100, Jan-Benedict Glaw wrote:
> > On Tue, 2007-01-30 21:23:34 +0100, Diego Calleja <[EMAIL PROTECTED]> wrote:
> > > El Tue, 30 Jan 2007 20:31:01 +0100 (MET), Jan Engelhardt <[EMAIL
>
Hi,
On Wed, Jan 31, 2007 at 10:13:12PM +0100, Jan-Benedict Glaw wrote:
> On Tue, 2007-01-30 21:23:34 +0100, Diego Calleja <[EMAIL PROTECTED]> wrote:
> > El Tue, 30 Jan 2007 20:31:01 +0100 (MET), Jan Engelhardt <[EMAIL
> > PROTECTED]> escribió:
> > > Don't they claim 50+? Already browsing
> > >
On 2/1/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
That lists seems really outdata.
- RaLink has gpl drivers (SerialMonkey maintains a better version),
- Cisco IPSEC can be replaced by the userspace tool vpnc (as far as the VPN
Concentrators I have to deal with),
It's a wiki[1], I invite
On Wed, 2007-01-31 19:24:54 +0100, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> How much different hardware does the (old)floppy.c do? I imagine that
> today, where floppies phase out, there will be, in descending order:
>
> * USB floppy drives (atm handled by sd.c, could be better to have sf.c)
On Tue, 2007-01-30 21:23:34 +0100, Diego Calleja <[EMAIL PROTECTED]> wrote:
> El Tue, 30 Jan 2007 20:31:01 +0100 (MET), Jan Engelhardt <[EMAIL PROTECTED]>
> escribió:
> > Don't they claim 50+? Already browsing
> > ftp://ftp.de.netbsd.org/pub/NetBSD/NetBSD-3.1 gives more than 2
> > screenfuls [à
On Jan 31 2007 11:54, Auke Kok wrote:
> Francois Romieu wrote:
>> Nicolas Mailhot <[EMAIL PROTECTED]> :
>> [...]
>> > incomplete NDAed documentation. If (as this offer implies) there are
>> > good
>> > driver authors waiting to do more drivering, why aren't those a
>> > priority?
>>
>> So far
Le mercredi 31 janvier 2007 à 12:12 -0800, Greg KH a écrit :
> On Wed, Jan 31, 2007 at 02:06:32PM +0100, Nicolas Mailhot wrote:
[Reordering for the sake of argument]
> > There are many out-of-tree drivers (ivtv, lirc, various webcam
> > drivers,
> > enhanced USB keyboard handlers...) with
On Wed, Jan 31, 2007 at 02:06:32PM +0100, Nicolas Mailhot wrote:
> Hi,
>
> I'd really love if the same offer was extended to GPL out-of-tree driver
> trees.
This kind of offer has _always_ been there for out-of-tree GPL drivers.
I have contacted many different groups and driver authors over the
Le mercredi 31 janvier 2007 à 20:29 +0100, Francois Romieu a écrit :
> Nicolas Mailhot <[EMAIL PROTECTED]> :
> [...]
> > incomplete NDAed documentation. If (as this offer implies) there are good
> > driver authors waiting to do more drivering, why aren't those a priority?
>
> So far nobody cared
On 1/30/07, Kumar Gala <[EMAIL PROTECTED]> wrote:
Out of interest are you was this geared to any particular SoC's/
architectures?
I had in mind the sort of ARM-, PPC-, and MIPS-based SoCs that wind up
in handhelds, mobiles, set-tops, and consumer-grade WiFi devices.
That's an area I know
Francois Romieu wrote:
Nicolas Mailhot <[EMAIL PROTECTED]> :
[...]
incomplete NDAed documentation. If (as this offer implies) there are good
driver authors waiting to do more drivering, why aren't those a priority?
So far nobody cared enough to maintain a list of said out-of-tree drivers.
Nicolas Mailhot <[EMAIL PROTECTED]> :
[...]
> incomplete NDAed documentation. If (as this offer implies) there are good
> driver authors waiting to do more drivering, why aren't those a priority?
So far nobody cared enough to maintain a list of said out-of-tree drivers.
--
Ueimor
-
To
On Jan 31 2007 13:58, Lennart Sorensen wrote:
>On Wed, Jan 31, 2007 at 07:24:54PM +0100, Jan Engelhardt wrote:
>> How much different hardware does the (old)floppy.c do? I imagine that
>> today, where floppies phase out, there will be, in descending order:
>>
>> * USB floppy drives (atm handled
On Wed, 31 Jan 2007, Jan Engelhardt wrote:
On Jan 31 2007 09:58, alan wrote:
On Wed, 31 Jan 2007, Jan Engelhardt wrote:
On Jan 30 2007 14:00, Roland Dreier wrote:
An uncharitable vendor might decide it's not worth publishing specs,
since the Linux guys can reverse engineer the Windows
On Wed, Jan 31, 2007 at 07:24:54PM +0100, Jan Engelhardt wrote:
> How much different hardware does the (old)floppy.c do? I imagine that
> today, where floppies phase out, there will be, in descending order:
>
> * USB floppy drives (atm handled by sd.c, could be better to have sf.c)
> * FDCs on
Putting the "codingstyle" control aside, often it's because things look
too hackish.
Also sometimes the authors know it's hackish, or just don't expect it
to be generally useful to the world. I happen to own an out-of-tree
filesystem which I have little desire to have reviewed for mainline:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 31 January 2007 15:49, Alan wrote:
> > Well, I have a long standing issue with pata_ali not detecting CD-ROM in
> > DMA mode. When I rarely watch DVD I rather boot into legacy IDE kernel
> > ...
>
> There is a general problem with some
On Jan 31 2007 09:58, alan wrote:
> On Wed, 31 Jan 2007, Jan Engelhardt wrote:
>> On Jan 30 2007 14:00, Roland Dreier wrote:
>> >
>> > An uncharitable vendor might decide it's not worth publishing specs,
>> > since the Linux guys can reverse engineer the Windows driver just as
>> > fast anyway.
On Jan 31 2007 18:24, Adrian Bunk wrote:
>On Wed, Jan 31, 2007 at 11:08:14AM +0100, Andi Kleen wrote:
>> Greg KH <[EMAIL PROTECTED]> writes:
>> >
>> > What? Throw a fresh-faced newbie instantly into the tar-pit of despair
>> > that floppy.c is? Do you want everyone just to run screaming from
On Wed, 31 Jan 2007, Jan Engelhardt wrote:
On Jan 30 2007 14:00, Roland Dreier wrote:
An uncharitable vendor might decide it's not worth publishing specs,
since the Linux guys can reverse engineer the Windows driver just as
fast anyway.
And ndiswrapper gives fire to just releasing the
On Jan 31 2007 08:34, David Hollis wrote:
>Conversely, I've seen many cases of drivers that are developed by the
>community, but kept out-of-kernel forever due to various reasons. Some
>of them are due to the code quality and the developers not accepting the
>feedback to get the drivers into
Jan Engelhardt wrote:
On Jan 30 2007 14:00, Roland Dreier wrote:
An uncharitable vendor might decide it's not worth publishing specs,
since the Linux guys can reverse engineer the Windows driver just as
fast anyway.
And ndiswrapper gives fire to just releasing the Windows one :(
Logically
On Jan 30 2007 14:00, Roland Dreier wrote:
>
>An uncharitable vendor might decide it's not worth publishing specs,
>since the Linux guys can reverse engineer the Windows driver just as
>fast anyway.
And ndiswrapper gives fire to just releasing the Windows one :(
Jan
--
-
To unsubscribe from
Greg KH <[EMAIL PROTECTED]> writes:
[...]
>> And there are plenty of documented devices that no one cares enough
>> about to submit a driver for.
>
> Any specific examples? I have a long list of people who wish to write
> new drivers but just don't know which hardware is not yet supported.
Maybe
On Wed, Jan 31, 2007 at 11:08:14AM +0100, Andi Kleen wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
> >
> > What? Throw a fresh-faced newbie instantly into the tar-pit of despair
> > that floppy.c is? Do you want everyone just to run screaming from
> > kernel development never to be seen again?
>
> When looking for a sata controller I came across several inexpensive
> ones based on an Initio chipset, and at first glance it seems that they
> have docs out there*: http://www.initio.com/products/sata.htm
>
> but no drivers yet. Just in case anyone is interested :)
2.6.20-mm, although it
Jeff Garzik wrote:
> Eric Sandeen wrote:
>> Jeff Garzik wrote:
>>> Roland Dreier wrote:
And I seem to recall there's more SATA chipset documentation than Jeff
Garzik has time to implement support for.
>>> I seriously doubt you can come up with even a single concrete example here.
>> Not
Eric Sandeen wrote:
Jeff Garzik wrote:
Roland Dreier wrote:
And I seem to recall there's more SATA chipset documentation than Jeff
Garzik has time to implement support for.
I seriously doubt you can come up with even a single concrete example here.
Not trying to slight Jeff here in any way,
Jeff Garzik wrote:
> Roland Dreier wrote:
>> And I seem to recall there's more SATA chipset documentation than Jeff
>> Garzik has time to implement support for.
>
> I seriously doubt you can come up with even a single concrete example here.
Not trying to slight Jeff here in any way, but I
When you say newbie? Do you mean coding newbie? Or... just someone who
hasn't done a driver before?
either way I'd like to be somewhat involved in the process so I see how
things are done.
--martin
Andi Kleen wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
>> What? Throw a fresh-faced newbie
On Tue, 2007-01-30 at 17:41 -0500, Jeff Garzik wrote:
>
> I think this is a quite fair criticism, and I would love to see
> someone
> step up and help with this sort of organization.
>
> For example, I didn't know that XGI graphics specs were available at
> all, otherwise it might have been
Hi,
I'd really love if the same offer was extended to GPL out-of-tree driver
trees.
There are many out-of-tree drivers (ivtv, lirc, various webcam drivers,
enhanced USB keyboard handlers...) with merging not planified or taking
ages.
The associated hardware is useful enough someone wrote a
> Well, I have a long standing issue with pata_ali not detecting CD-ROM in DMA
> mode. When I rarely watch DVD I rather boot into legacy IDE kernel ...
There is a general problem with some ATAPI devices and the probe logic
currently. The old IDE code has some workarounds that the new libata
layer
On 31/01/07, Trent Waddington <[EMAIL PROTECTED]> wrote:
On 1/31/07, Jesper Juhl <[EMAIL PROTECTED]> wrote:
> Sounds like a fun little project. I'll bite.
Let me know when you have something and I'll go buy those floppies,
test it and fix a bug or two if I find 'em.
Sure. Will do. Thanks.
--
On 1/31/07, Jesper Juhl <[EMAIL PROTECTED]> wrote:
Sounds like a fun little project. I'll bite.
Let me know when you have something and I'll go buy those floppies,
test it and fix a bug or two if I find 'em.
Trent
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On 31 Jan 2007 11:08:14 +0100, Andi Kleen <[EMAIL PROTECTED]> wrote:
Greg KH <[EMAIL PROTECTED]> writes:
>
> What? Throw a fresh-faced newbie instantly into the tar-pit of despair
> that floppy.c is? Do you want everyone just to run screaming from
> kernel development never to be seen again?
Greg KH <[EMAIL PROTECTED]> writes:
>
> What? Throw a fresh-faced newbie instantly into the tar-pit of despair
> that floppy.c is? Do you want everyone just to run screaming from
> kernel development never to be seen again?
Doing a from-scratch rewrite of floppy.c only supporting new
hardware
Greg KH [EMAIL PROTECTED] writes:
What? Throw a fresh-faced newbie instantly into the tar-pit of despair
that floppy.c is? Do you want everyone just to run screaming from
kernel development never to be seen again?
Doing a from-scratch rewrite of floppy.c only supporting new
hardware and no
On 31 Jan 2007 11:08:14 +0100, Andi Kleen [EMAIL PROTECTED] wrote:
Greg KH [EMAIL PROTECTED] writes:
What? Throw a fresh-faced newbie instantly into the tar-pit of despair
that floppy.c is? Do you want everyone just to run screaming from
kernel development never to be seen again?
Doing a
On 1/31/07, Jesper Juhl [EMAIL PROTECTED] wrote:
Sounds like a fun little project. I'll bite.
Let me know when you have something and I'll go buy those floppies,
test it and fix a bug or two if I find 'em.
Trent
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
On 31/01/07, Trent Waddington [EMAIL PROTECTED] wrote:
On 1/31/07, Jesper Juhl [EMAIL PROTECTED] wrote:
Sounds like a fun little project. I'll bite.
Let me know when you have something and I'll go buy those floppies,
test it and fix a bug or two if I find 'em.
Sure. Will do. Thanks.
--
Well, I have a long standing issue with pata_ali not detecting CD-ROM in DMA
mode. When I rarely watch DVD I rather boot into legacy IDE kernel ...
There is a general problem with some ATAPI devices and the probe logic
currently. The old IDE code has some workarounds that the new libata
layer
Hi,
I'd really love if the same offer was extended to GPL out-of-tree driver
trees.
There are many out-of-tree drivers (ivtv, lirc, various webcam drivers,
enhanced USB keyboard handlers...) with merging not planified or taking
ages.
The associated hardware is useful enough someone wrote a
On Tue, 2007-01-30 at 17:41 -0500, Jeff Garzik wrote:
I think this is a quite fair criticism, and I would love to see
someone
step up and help with this sort of organization.
For example, I didn't know that XGI graphics specs were available at
all, otherwise it might have been something
When you say newbie? Do you mean coding newbie? Or... just someone who
hasn't done a driver before?
either way I'd like to be somewhat involved in the process so I see how
things are done.
--martin
Andi Kleen wrote:
Greg KH [EMAIL PROTECTED] writes:
What? Throw a fresh-faced newbie
Jeff Garzik wrote:
Roland Dreier wrote:
And I seem to recall there's more SATA chipset documentation than Jeff
Garzik has time to implement support for.
I seriously doubt you can come up with even a single concrete example here.
Not trying to slight Jeff here in any way, but I thought I'd
Eric Sandeen wrote:
Jeff Garzik wrote:
Roland Dreier wrote:
And I seem to recall there's more SATA chipset documentation than Jeff
Garzik has time to implement support for.
I seriously doubt you can come up with even a single concrete example here.
Not trying to slight Jeff here in any way,
Jeff Garzik wrote:
Eric Sandeen wrote:
Jeff Garzik wrote:
Roland Dreier wrote:
And I seem to recall there's more SATA chipset documentation than Jeff
Garzik has time to implement support for.
I seriously doubt you can come up with even a single concrete example here.
Not trying to slight
When looking for a sata controller I came across several inexpensive
ones based on an Initio chipset, and at first glance it seems that they
have docs out there*: http://www.initio.com/products/sata.htm
but no drivers yet. Just in case anyone is interested :)
2.6.20-mm, although it can't
On Wed, Jan 31, 2007 at 11:08:14AM +0100, Andi Kleen wrote:
Greg KH [EMAIL PROTECTED] writes:
What? Throw a fresh-faced newbie instantly into the tar-pit of despair
that floppy.c is? Do you want everyone just to run screaming from
kernel development never to be seen again?
Doing a
Greg KH [EMAIL PROTECTED] writes:
[...]
And there are plenty of documented devices that no one cares enough
about to submit a driver for.
Any specific examples? I have a long list of people who wish to write
new drivers but just don't know which hardware is not yet supported.
Maybe not
On Jan 30 2007 14:00, Roland Dreier wrote:
An uncharitable vendor might decide it's not worth publishing specs,
since the Linux guys can reverse engineer the Windows driver just as
fast anyway.
And ndiswrapper gives fire to just releasing the Windows one :(
Jan
--
-
To unsubscribe from this
Jan Engelhardt wrote:
On Jan 30 2007 14:00, Roland Dreier wrote:
An uncharitable vendor might decide it's not worth publishing specs,
since the Linux guys can reverse engineer the Windows driver just as
fast anyway.
And ndiswrapper gives fire to just releasing the Windows one :(
Logically
On Jan 31 2007 08:34, David Hollis wrote:
Conversely, I've seen many cases of drivers that are developed by the
community, but kept out-of-kernel forever due to various reasons. Some
of them are due to the code quality and the developers not accepting the
feedback to get the drivers into shape
On Wed, 31 Jan 2007, Jan Engelhardt wrote:
On Jan 30 2007 14:00, Roland Dreier wrote:
An uncharitable vendor might decide it's not worth publishing specs,
since the Linux guys can reverse engineer the Windows driver just as
fast anyway.
And ndiswrapper gives fire to just releasing the
On Jan 31 2007 18:24, Adrian Bunk wrote:
On Wed, Jan 31, 2007 at 11:08:14AM +0100, Andi Kleen wrote:
Greg KH [EMAIL PROTECTED] writes:
What? Throw a fresh-faced newbie instantly into the tar-pit of despair
that floppy.c is? Do you want everyone just to run screaming from
kernel
On Jan 31 2007 09:58, alan wrote:
On Wed, 31 Jan 2007, Jan Engelhardt wrote:
On Jan 30 2007 14:00, Roland Dreier wrote:
An uncharitable vendor might decide it's not worth publishing specs,
since the Linux guys can reverse engineer the Windows driver just as
fast anyway.
And
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 31 January 2007 15:49, Alan wrote:
Well, I have a long standing issue with pata_ali not detecting CD-ROM in
DMA mode. When I rarely watch DVD I rather boot into legacy IDE kernel
...
There is a general problem with some ATAPI
Putting the codingstyle control aside, often it's because things look
too hackish.
Also sometimes the authors know it's hackish, or just don't expect it
to be generally useful to the world. I happen to own an out-of-tree
filesystem which I have little desire to have reviewed for mainline:
only
101 - 200 of 376 matches
Mail list logo
