Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*RFC\:\s+Network\s+Device\s+Driver\s+Group\s+proposal\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*RFC\:\s+Network\s+Device\s+Driver\s+Group\s+proposal\s*$/: 14 ]

Total 14 documents matching your query.

1. nds (score: 1): Author: Kumar Amritaluru <praveen@xxxxxxxxxxxx>; Date: Mon, 24 May 2004 04:49:45 -0400; This is a RFC for the start of a Network Device Driver Group. There is currently no central group that I am aware of that hardware/chipset manufacturer companies can contact to assist in writing/mant; /archives/netdev/2004-05/msg00276.html (10,141 bytes)
2. ing (score: 1): Author: xxxxxxx>; Date: Mon, 24 May 2004 11:39:19 -0700; On Mon, 24 May 2004 04:49:45 -0400 OSDL does have the ability to host Special Interest Groups (SIG's). There are two existing SIG's one for security, and another for storage. It would make sense to h; /archives/netdev/2004-05/msg00294.html (9,256 bytes)
3. ult (score: 1): Author:; Date: Mon, 24 May 2004 15:27:44 -0400; Stephen Hemminger wrote: Probably there needs to be a strong reason to add more organization to a already mostly functional process. That's my feeling. netdev list seems to work. Jeff; /archives/netdev/2004-05/msg00297.html (8,570 bytes)
4. ult (score: 1): Author: itry Torokhov <dtor_core@xxxxxxxxxxxxx>; Date: Mon, 24 May 2004 13:05:41 -0700; I agree, and Luis (mcgrof) should point out any specific issues so that they might be resolved... -- ~Randy; /archives/netdev/2004-05/msg00304.html (8,652 bytes)
5. sal (score: 1): Author: xxx>; Date: Mon, 24 May 2004 15:41:17 -0400; I think the netdev list is great. In fact, it's superb. But I think network driver developers need more than a list. I think it'd be great if we had a central group that can serve as resource for leg; /archives/netdev/2004-05/msg00305.html (12,354 bytes)
6. sal (score: 1): Author: xxxxxxxxxxxxxxxxxxx (Luis R. Rodriguez); Date: Mon, 24 May 2004 13:20:41 -0700; For a lot of reasons, OSDL won't usually sign NDA's especially the boilerplate kind that most companies provide. The NDA really needs to be with driver author; even then the restrictions can be unpa; /archives/netdev/2004-05/msg00306.html (10,774 bytes)
7. sal (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Mon, 24 May 2004 23:17:32 +0200; Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxxxxxx> : May I suggest the following thread on dri-devel: I enjoy working on drivers for which the datasheets are publically available. I do not buy your "cor; /archives/netdev/2004-05/msg00307.html (9,633 bytes)
8. RFC: Network Device Driver Group proposal (score: 1): Author: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxxxxxxxxxxxx>; Date: Mon, 24 May 2004 04:49:45 -0400; This is a RFC for the start of a Network Device Driver Group. There is currently no central group that I am aware of that hardware/chipset manufacturer companies can contact to assist in writing/mant; /archives/netdev/2004-05/msg00794.html (10,141 bytes)
9. Re: RFC: Network Device Driver Group proposal (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Mon, 24 May 2004 11:39:19 -0700; On Mon, 24 May 2004 04:49:45 -0400 " OSDL does have the ability to host Special Interest Groups (SIG's). There are two existing SIG's one for security, and another for storage. It would make sense to; /archives/netdev/2004-05/msg00812.html (9,314 bytes)
10. Re: RFC: Network Device Driver Group proposal (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Mon, 24 May 2004 15:27:44 -0400; That's my feeling. netdev list seems to work. Jeff; /archives/netdev/2004-05/msg00815.html (8,615 bytes)
11. Re: RFC: Network Device Driver Group proposal (score: 1): Author: "Randy.Dunlap" <rddunlap@xxxxxxxx>; Date: Mon, 24 May 2004 13:05:41 -0700; I agree, and Luis (mcgrof) should point out any specific issues so that they might be resolved... -- ~Randy; /archives/netdev/2004-05/msg00822.html (8,760 bytes)
12. Re: RFC: Network Device Driver Group proposal (score: 1): Author: mcgrof@xxxxxxxxxxxxxxxxxxxx (Luis R. Rodriguez); Date: Mon, 24 May 2004 15:41:17 -0400; I think the netdev list is great. In fact, it's superb. But I think network driver developers need more than a list. I think it'd be great if we had a central group that can serve as resource for leg; /archives/netdev/2004-05/msg00823.html (12,445 bytes)
13. Re: RFC: Network Device Driver Group proposal (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Mon, 24 May 2004 13:20:41 -0700; For a lot of reasons, OSDL won't usually sign NDA's especially the boilerplate kind that most companies provide. The NDA really needs to be with driver author; even then the restrictions can be unpa; /archives/netdev/2004-05/msg00824.html (10,892 bytes)
14. Re: RFC: Network Device Driver Group proposal (score: 1): Author: Francois Romieu <romieu@xxxxxxxxxxxxx>; Date: Mon, 24 May 2004 23:17:32 +0200; Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxxxxxx> : [...] May I suggest the following thread on dri-devel: I enjoy working on drivers for which the datasheets are publically available. I do not buy you; /archives/netdev/2004-05/msg00825.html (9,793 bytes)

Current List: 1 - 14
Page: [1]