public inbox for
 help / color / mirror / Atom feed
Subject: [Bug 1001466] /dev/null serial driver
Date: Wed, 15 Feb 2012 20:46:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Please do not reply to this email. Use the web interface provided at:

--- Comment #3 from Sergei Gavrikov <> 2012-02-15 20:45:18 GMT ---
On Comment #0
> Try to mimick /dev/null. (inspired by loop serial driver.) Comments
> welcome, maybe the semantics aren't close enough to Un*x but it should
> do the job for most cases. The doc may need to be rewritten?

It seemed to me your interpretation of /dev/null will arise some
confusions for some users. Below are mine.

Mess #1

  I would avoid the same mimic (and naming). In UNIX-like operating
  systems, /dev/null is a special *file* and not a serial device.

  % stty -aF /dev/null
  stty: /dev/null: Inappropriate ioctl for device

As you can see /dev/null is not some terminal line (serial device).
Well, eCos != *nix, but, I would avoid the ability to configure the
/dev/null as a serial device under eCos.

Mess #2

  A read on /dev/null would not block process (thread), it does return
  EOF, and you offer in your documentation to enter an ability of the
  blocking read on /dev/null as an option.

Mess #3

  IMO, if anyone will see those words together in CDL (I mean 'serial'
  and 'null'), under eCos dev/serial/null, then he would think, Great!
  There is 'nullmodem' device in eCos! Come check my guess 

  And after reading your documentation, they will think, Nope! They
  provide something very special (special null device :-)


I do not want to break your idea. IMHO, the main mess here is naming and
your free interpretation of /dev/null. You try to implement some serial
device like a "tear off" nullmodem, but what is bad with a "nullmodem"
abstraction for your purposes? And eCos serial loop driver (as you could
see) is a half of nullmodem itself.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2012-02-15 20:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 17:39 [Bug 1001466] New: " bugzilla-daemon
2012-01-27 19:14 ` [Bug 1001466] " bugzilla-daemon
2012-02-15 13:47 ` bugzilla-daemon
2012-02-15 13:48 ` bugzilla-daemon
2012-02-15 20:46 ` bugzilla-daemon [this message]
2012-02-16  9:55 ` bugzilla-daemon
2012-02-16 14:01   ` Grant Edwards
2012-02-16 12:20 ` bugzilla-daemon
2012-02-16 14:21 ` bugzilla-daemon
2012-02-16 15:06 ` bugzilla-daemon
2012-02-16 15:39 ` bugzilla-daemon
2012-02-16 15:58 ` bugzilla-daemon
2012-02-16 16:26 ` bugzilla-daemon
2012-02-16 16:37 ` bugzilla-daemon
2012-02-16 16:49 ` bugzilla-daemon
2012-02-16 17:21 ` bugzilla-daemon
2012-02-17  6:17 ` bugzilla-daemon
2012-02-18 19:38 ` bugzilla-daemon

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:

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

  git send-email \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).