From: Henk <Henk.Vergonet@gmail.com>
To: randy_dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] new 7-segments char translation API
Date: Tue, 21 Jun 2005 23:30:09 +0200 [thread overview]
Message-ID: <20050621213009.GA2122@god.dyndns.org> (raw)
In-Reply-To: <20050606091942.2c31bb98.rdunlap@xenotime.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1968 bytes --]
On Mon, Jun 06, 2005 at 09:19:42AM -0700, randy_dunlap wrote:
> On Mon, 6 Jun 2005 11:26:08 +0200 Henk wrote:
>
> | On Sun, Jun 05, 2005 at 12:53:29AM +0200, Edgar Toernig wrote:
> | > By your reasoning /usr/dict/words had to be in the kernel,
> | > too.
> |
> | Well by my reasoning you should, if possible, define some usefull
> | standards that will allow te reuse of these dictionaries within other
> | applications.
> |
> | And while we're on the subject of whats IN or OUT, (and I'll bet if you
> | ask 10 kernel developers you'll get 10 answers but I try anyway ;)
> |
> | In my philosophy the OS (kernel + device drivers) is an abstraction of
> | the machine, it should present the 'machine' in such a way that allows
> | for other abstractions such as a word processor to operate without having
> | to know the specifics of hardware devices.
>
> The abstraction also includes libraries, and if lib7segment
> could do this from userspace, that's where it should reside.
> I'm not saying that it can, but if it can, then that's the
> desired place for it.
>
Sorry for the late response,
The patch that was at the beginning of this thread is just a standard,
and just enough so a userspace program would never have to know anything
about 7 segments. And its just enough a device driver that needs to know
about this can implement it in a way that is portable and standardised.
I would, with all the love of the world create an userspace lib7segment for
you guys, but all I can think of is just this linux include file.
Well I think that the real issue here is that many of the kernel
developers feel that there´s to much fluff & features in the kernel
already.
>From an operational perspective I imagine its becomming harder and harder
to manage kernel code so I can understand people when they are
saying f**k off with 7-segments Ive got bigger fish to fry.
No offense taken, I just hope I didnt offend anyone either.
Ill be back,)
Henk Vergonet
next prev parent reply other threads:[~2005-06-21 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 22:07 Henk
2005-06-01 8:43 ` Jan-Benedict Glaw
2005-06-01 10:04 ` Henk
2005-06-01 12:33 ` Clemens Koller
2005-06-03 20:50 ` Henk
2005-06-04 20:44 ` Henk
2005-06-04 22:53 ` Edgar Toernig
2005-06-06 9:26 ` Henk
2005-06-06 16:19 ` randy_dunlap
2005-06-21 21:30 ` Henk [this message]
2005-06-04 15:24 ` Pavel Machek
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=20050621213009.GA2122@god.dyndns.org \
--to=henk.vergonet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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®