public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stuart Lynne <sl@fireplug.net>
To: Dan Hollis <goemon@anime.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [RFC-2] Configuring Synchronous Interfaces in Linux
Date: Tue, 5 Dec 2000 17:55:17 -0800	[thread overview]
Message-ID: <20001205175517.I13431@fireplug.net> (raw)
In-Reply-To: <E143THN-0000A1-00@the-village.bc.nu> <Pine.LNX.4.30.0012051733020.11374-100000@anime.net>
In-Reply-To: <Pine.LNX.4.30.0012051733020.11374-100000@anime.net>; from goemon@anime.net on Tue, Dec 05, 2000 at 05:34:50PM -0800

On Tue, Dec 05, 2000 at 05:34:50PM -0800, Dan Hollis wrote:
> On Wed, 6 Dec 2000, Alan Cox wrote:
> > > Ditto, we have an adsl driver that we setup by overloading various otherwise
> > > unused options in ifconfig (mem_start, io_addr etc) to do this. Cheaper and
> > > faster than writing yet another ioctl using device configuration agent, but
> > > distasteful non the less.
> > Generic is not always good , thats why we have SIOCDEVPRIVATE. One thing Im
> > pondering is if we should make the hardware config ioctl take a hardware type
> > ident with each struct. That would help make all the ethernet agree, all the
> > wan agree, all the ADSL agree without making a nasty mess.
> 
> Id be up for that, but its hard to standardize on IOCTLs without people
> publishing their drivers, as long as people hide their code we dont know
> what everyone else is doing config interface wise...
> 
> Lets see the code, people...

We are trying to get permission from the customer to release it.

-- 
                                            __O 
Fireplug - a Lineo company                _-\<,_ 
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <sl@fireplug.net>         www.lineo.com         604-461-7532
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-06  2:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-05 22:55 [RFC-2] Configuring Synchronous Interfaces in Linux Stuart Lynne
2000-12-06  1:21 ` Alan Cox
2000-12-06  1:34   ` Dan Hollis
2000-12-06  1:55     ` Stuart Lynne [this message]
2000-12-07  0:14   ` Krzysztof Halasa
2000-12-07 14:09     ` Alan Cox
2000-12-07 14:12       ` Jeff Garzik
2000-12-07 14:40         ` Alan Cox
2000-12-09 22:33           ` parport0 problem ebi4
2001-03-19 16:28       ` [RFC-2] Configuring Synchronous Interfaces in Linux Krzysztof Halasa
     [not found] <Pine.LNX.4.30.0012051925330.6718-100000@pc24.sr.bham.ac.uk>
2000-12-05 19:46 ` Ivan Passos
  -- strict thread matches above, loose matches on Subject: below --
2000-12-05  5:58 Ivan Passos
2000-12-05  9:38 ` Francois Romieu
2000-12-05 19:17   ` Ivan Passos
2000-12-05  9:41 ` Alan Cox
2000-12-05 15:15   ` Greg Parrott
2000-12-05 19:23   ` Ivan Passos
2000-12-05 20:41     ` Peter Samuelson
2000-12-05 21:56     ` Alan Cox
2000-12-05 14:43 ` Matthew G. Marsh
2000-12-05 19:40   ` Ivan Passos
2000-12-05 15:18 ` Paul Fulghum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001205175517.I13431@fireplug.net \
    --to=sl@fireplug.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=goemon@anime.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox