All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.17 /dev/ports
Date: Thu, 23 May 2002 20:05:08 +0200	[thread overview]
Message-ID: <3CED2F54.8000809@evision-ventures.com> (raw)
In-Reply-To: <mailman.1022085725.386.linux-kernel2news@redhat.com> <200205231707.g4NH74K06402@devserv.devel.redhat.com>

Użytkownik Pete Zaitcev napisał:
>>Anybody: if you've ever used /dev/ports, holler _now_.
>>
>>		Linus
> 
> 
> I often use it as an alternative to #include <asm/io.h>,
> which you decreed illegal. I understand <sys/io.h> is a legal
> alternative, but a bunch of platforms forget to
> include <sys/io.h>, for instance Jes cried bloody murder
> when asked to add it to ia-64. But if you decide to drop /dev/port
> I can tough it out. Solaris lives without it, and so can we.
> 
> I saw this whining about outl not implemented for
> write(fd, &my_int, 4), and I think the guy had a little point.
> Though if he wanted it, he ought to submit a patch.


Hey and finally if someone want's to use /dev/port for
developement on some slow control experimental hardware for example.
Why doesn't he just delete the - signs at the front lines
of the patch deleting it plus module register/unregister trivia and
compile it as a *separate* character device module ?
That's linux - you have the source, so use it.
You wan't to cheat around the OS abstractions - do it for yourself!
There is no requirement that it has to be
permanently in the mainline kernel where it tends to
attract people who shouldn't have used it in first place
for generic stuff like kbd rate settings and clock device
manipulation.


  reply	other threads:[~2002-05-23 19:08 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1022085725.386.linux-kernel2news@redhat.com>
2002-05-23 17:07 ` [PATCH] 2.5.17 /dev/ports Pete Zaitcev
2002-05-23 18:05   ` Martin Dalecki [this message]
2002-05-23 19:54     ` Linus Torvalds
2002-05-23 19:31       ` Martin Dalecki
2002-05-23 21:22         ` Christer Weinigel
2002-05-23 21:37           ` Pete Zaitcev
2002-05-23 20:53             ` Martin Dalecki
2002-05-24  5:39           ` Robert Schwebel
2002-05-23 21:29         ` Pete Zaitcev
2002-05-22 16:30 James Simmons
2002-05-22 17:25 ` Alan Cox
2002-05-22 17:39   ` James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2002-05-21  5:16 Linux-2.5.17 Linus Torvalds
2002-05-22  9:05 ` [PATCH] 2.5.17 /dev/ports Martin Dalecki
2002-05-22 10:42   ` Paul Mackerras
2002-05-22  9:46     ` Martin Dalecki
2002-05-22 10:54     ` David S. Miller
2002-05-22 10:13       ` Martin Dalecki
2002-05-22 11:26         ` Russell King
2002-05-22 10:40           ` Martin Dalecki
2002-05-22 11:58             ` Richard B. Johnson
2002-05-22 12:36             ` Russell King
2002-05-22 13:23               ` Alan Cox
2002-05-22 12:31                 ` Martin Dalecki
2002-05-22 12:44           ` Alan Cox
2002-05-22 12:32             ` Martin Dalecki
2002-05-22 15:05               ` Alan Cox
2002-05-22 13:05       ` Alan Cox
2002-05-22 12:38         ` Martin Dalecki
2002-05-22 15:04           ` Alan Cox
2002-05-22 13:53             ` Martin Dalecki
2002-05-22 15:03               ` Lars Marowsky-Bree
2002-05-22 15:07               ` Padraig Brady
2002-05-22 14:07                 ` Martin Dalecki
2002-05-22 15:21                   ` Dave Jones
2002-05-22 15:19               ` Dave Jones
2002-05-22 15:31               ` Alan Cox
2002-05-27  9:04               ` Pavel Machek
2002-05-22 14:54             ` Alexander Viro
2002-05-22 15:24               ` Alan Cox
2002-05-22 15:10                 ` Alexander Viro
2002-07-22 12:20                   ` Ruth Ivimey-Cook
2002-05-23  7:30               ` Rusty Russell
2002-05-23  6:44                 ` Martin Dalecki
2002-05-23  8:26                   ` Rusty Russell
2002-05-22 13:16   ` Padraig Brady
2002-05-22 12:30     ` Martin Dalecki
2002-05-22 13:50       ` Sebastian Droege
2002-05-22 13:52     ` Alan Cox
2002-05-22 13:49       ` Vojtech Pavlik
2002-05-22 12:51         ` Martin Dalecki
2002-05-22 13:56           ` Vojtech Pavlik
2002-05-22 14:58             ` Alan Cox
2002-05-22 13:49               ` Martin Dalecki
2002-05-22 14:42               ` Vojtech Pavlik
2002-05-22 13:59           ` Alexander Viro
2002-05-22 13:12             ` Martin Dalecki
2002-05-22 14:33               ` Alexander Viro
2002-05-22 13:40                 ` Martin Dalecki
2002-05-22 13:16             ` Martin Dalecki
2002-05-22 14:34               ` Alexander Viro
2002-05-22 16:31               ` James Simmons
2002-05-22 14:12             ` Vojtech Pavlik
2002-05-27  9:07             ` Pavel Machek
2002-05-22 15:00         ` Alan Cox
2002-05-22 14:43           ` Vojtech Pavlik
2002-05-22 16:28   ` Linus Torvalds
2002-05-22 17:22     ` Alan Cox
2002-05-22 16:17       ` Martin Dalecki
2002-05-22 17:30         ` Russell King
2002-05-22 16:36           ` Martin Dalecki
2002-05-22 17:36           ` Alexander Viro
2002-05-22 17:46         ` Alan Cox
2002-05-26 13:53         ` Riley Williams
2002-05-26 15:28           ` Vojtech Pavlik
2002-05-26 15:39             ` Riley Williams
2002-05-23 10:10     ` Martin Diehl

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=3CED2F54.8000809@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=zaitcev@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.