Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*net\s+driver\s+directory\s+moves\s+for\s+2\.5\s*$/: 14 ]

Total 14 documents matching your query.

1. net driver directory moves for 2.5 (score: 1)
Author: xxxxxxxxxxxxxx>
Date: Fri, 22 Jun 2001 01:00:42 -0400
I've mentioned this before, but since its impending, I wanted to bring it up again: I'd like to shuffle some drivers into sub-directories, and shrink drivers/net a bit. This is NOT a wholesale reorga
/archives/netdev/2001-06/msg00154.html (7,908 bytes)

2. Re: net driver directory moves for 2.5 (score: 1)
Author: een <ak@xxxxxx>
Date: 22 Jun 2001 15:29:12 +0200
Where do Lance ISA drivers go? It seems like a somewhat random choice of groups to me, ie. 8390, tulip & Lance directories kinda match but ISA and 3Com are orthogonal to this. Jes
/archives/netdev/2001-06/msg00161.html (8,609 bytes)

3. Re: net driver directory moves for 2.5 (score: 1)
Author: jes@xxxxxxxxxx>
Date: Fri, 22 Jun 2001 16:38:49 +0100 (IST)
what about the 3c503... that's a 3COM, 8390, ISA network card :-) he's the bext example I can think of ... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied@xxxxxxxxx p
/archives/netdev/2001-06/msg00162.html (9,028 bytes)

4. Re: net driver directory moves for 2.5 (score: 1)
Author: ugh@xxxxxxxxxx>
Date: Sat, 23 Jun 2001 03:55:22 +1200
drivers/net/<chipset-flavour>/blah for those that apply drivers/net/<vendor>/blah for 3com chips that don't fit sort of thing seems reasonable. Maybe even for some architectures doing arch or sub spe
/archives/netdev/2001-06/msg00164.html (8,655 bytes)

5. Re: net driver directory moves for 2.5 (score: 1)
Author: d <cw@xxxxxxxx>
Date: Fri, 22 Jun 2001 14:01:52 -0400
It's not a random choice of groups at all, it's where common code will get grouped together the most. Drivers that fit into 8390, tulip, or lance categories will go into those directories. Which woul
/archives/netdev/2001-06/msg00165.html (9,285 bytes)

6. Re: net driver directory moves for 2.5 (score: 1)
Author: .hen@xxxxxxxxx>
Date: 24 Jun 2001 16:16:13 +0200
No no no no Those Sun SBUS cards are using the same chips found on other cards, we should be able to share wherever possible. Keep drivers out of arch specific directories. Jes
/archives/netdev/2001-06/msg00169.html (8,643 bytes)

7. Re: net driver directory moves for 2.5 (score: 1)
Author: jes@xxxxxxxxxx>
Date: 24 Jun 2001 16:18:14 +0200
I still think you should be consistent and stick to chip specific directories. Some of those ISA drivers support both ISA, EISA and PCI cards, some fall into multiple categories as mentioned earlier
/archives/netdev/2001-06/msg00170.html (9,068 bytes)

8. net driver directory moves for 2.5 (score: 1)
Author: Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx>
Date: Fri, 22 Jun 2001 01:00:42 -0400
I've mentioned this before, but since its impending, I wanted to bring it up again: I'd like to shuffle some drivers into sub-directories, and shrink drivers/net a bit. This is NOT a wholesale reorga
/archives/netdev/2001-06/msg00344.html (7,908 bytes)

9. Re: net driver directory moves for 2.5 (score: 1)
Author: Jes Sorensen <jes@xxxxxxxxxx>
Date: 22 Jun 2001 15:29:12 +0200
Where do Lance ISA drivers go? It seems like a somewhat random choice of groups to me, ie. 8390, tulip & Lance directories kinda match but ISA and 3Com are orthogonal to this. Jes
/archives/netdev/2001-06/msg00351.html (8,634 bytes)

10. Re: net driver directory moves for 2.5 (score: 1)
Author: Dave Airlie <airlied@xxxxxxxxx>
Date: Fri, 22 Jun 2001 16:38:49 +0100 (IST)
what about the 3c503... that's a 3COM, 8390, ISA network card :-) he's the bext example I can think of ... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied@xxxxxxxxx p
/archives/netdev/2001-06/msg00352.html (9,065 bytes)

11. Re: net driver directory moves for 2.5 (score: 1)
Author: Chris Wedgwood <cw@xxxxxxxx>
Date: Sat, 23 Jun 2001 03:55:22 +1200
drivers/net/<chipset-flavour>/blah for those that apply drivers/net/<vendor>/blah for 3com chips that don't fit sort of thing seems reasonable. Maybe even for some architectures doing arch or sub spe
/archives/netdev/2001-06/msg00354.html (8,872 bytes)

12. Re: net driver directory moves for 2.5 (score: 1)
Author: Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx>
Date: Fri, 22 Jun 2001 14:01:52 -0400
It's not a random choice of groups at all, it's where common code will get grouped together the most. Drivers that fit into 8390, tulip, or lance categories will go into those directories. Which woul
/archives/netdev/2001-06/msg00355.html (9,332 bytes)

13. Re: net driver directory moves for 2.5 (score: 1)
Author: Jes Sorensen <jes@xxxxxxxxxx>
Date: 24 Jun 2001 16:16:13 +0200
No no no no Those Sun SBUS cards are using the same chips found on other cards, we should be able to share wherever possible. Keep drivers out of arch specific directories. Jes
/archives/netdev/2001-06/msg00359.html (8,769 bytes)

14. Re: net driver directory moves for 2.5 (score: 1)
Author: Jes Sorensen <jes@xxxxxxxxxx>
Date: 24 Jun 2001 16:18:14 +0200
I still think you should be consistent and stick to chip specific directories. Some of those ISA drivers support both ISA, EISA and PCI cards, some fall into multiple categories as mentioned earlier
/archives/netdev/2001-06/msg00360.html (9,140 bytes)


This search system is powered by Namazu