From: Abraham vd Merwe <abraham@2d3d.co.za>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ethtool documentation
Date: Wed, 7 Aug 2002 10:02:34 +0200 [thread overview]
Message-ID: <20020807100234.B9263@crystal.2d3d.co.za> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0208060834030.10089-100000@dragon.pdx.osdl.net>; from rddunlap@osdl.org on Tue, Aug 06, 2002 at 08:41:13 -0700
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
Hi Randy!
> | Wouldn't it have been better to make this 'n character device which can
> | be read from / written to just like a normal file (/dev/nvram-like
> | interface) -
> | that way applications can actually use unused eeprom space.
>
> I wouldn't care for this. There's nothing 'normal' about this
> EEPROM space, and apps generally won't know where there might be
> some 'unused eeprom space'.
That's not true. Sure, it may not be useful in your average setup, but there
are some cases where it might be useful, e.g. in embedded systems.
--
Regards
Abraham
Faith is under the left nipple.
-- Martin Luther
__________________________________________________________
Abraham vd Merwe - 2d3D, Inc.
Device Driver Development, Outsourcing, Embedded Systems
Cell: +27 82 565 4451 Snailmail:
Tel: +27 21 761 7549 Block C, Aintree Park
Fax: +27 21 761 7648 Doncaster Road
Email: abraham@2d3d.co.za Kenilworth, 7700
Http: http://www.2d3d.com South Africa
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-08-07 7:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 15:41 Randy.Dunlap
2002-08-06 19:24 ` Richard B. Johnson
2002-08-06 19:40 ` Chris Friesen
2002-08-06 19:44 ` Randy.Dunlap
2002-08-06 20:03 ` Richard B. Johnson
2002-08-06 20:04 ` Randy.Dunlap
2002-08-06 20:36 ` Ben Greear
2002-08-06 21:15 ` Tim Hockin
2002-08-07 1:42 ` Richard B. Johnson
2002-08-07 3:33 ` Tim Hockin
2002-08-06 21:58 ` Alan Cox
2002-08-06 20:42 ` Randy.Dunlap
2002-08-06 22:27 ` Alan Cox
2002-08-19 19:00 ` Mark H. Wood
2002-08-07 1:57 ` Richard B. Johnson
2002-08-07 11:47 ` Alan Cox
2002-08-07 2:54 ` Ryan Anderson
2002-08-07 5:32 ` Dax Kelson
2002-08-07 6:30 ` Jonathan Lundell
2002-08-07 11:47 ` Alan Cox
2002-08-08 1:07 ` Peter Samuelson
2002-08-07 11:18 ` Richard B. Johnson
2002-08-07 12:05 ` Abraham vd Merwe
2002-08-07 18:44 ` Bernd Eckenfels
2002-08-07 20:16 ` erik
2002-08-07 8:02 ` Abraham vd Merwe [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 9:18 Helge Hafting
2002-08-07 18:16 Leif Sawyer
2002-08-06 20:57 Leif Sawyer
2002-08-07 1:51 ` Richard B. Johnson
2002-08-07 10:53 ` Jamie Lokier
2002-08-05 11:46 Abraham vd Merwe
2002-08-05 15:42 ` Jeff Garzik
2002-08-05 19:06 ` Tim Hockin
2002-08-05 19:16 ` Jeff Garzik
2002-08-05 19:30 ` Jonathan Lundell
2002-08-05 20:20 ` Jeff Garzik
2002-08-06 10:17 ` Abraham vd Merwe
2002-08-06 10:07 ` David S. Miller
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=20020807100234.B9263@crystal.2d3d.co.za \
--to=abraham@2d3d.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®