This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1001466] /dev/null serial driver
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: unassigned at bugs dot ecos dot sourceware dot org
- Date: Thu, 16 Feb 2012 17:21:03 +0000
- Subject: [Bug 1001466] /dev/null serial driver
- Auto-submitted: auto-generated
- References: <bug-1001466-777@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001466
--- Comment #13 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2012-02-16 17:21:00 GMT ---
(In reply to comment #12)
> (In reply to comment #11)
> > (In reply to comment #10)
> >
> > [snip]
> >
> > > > And what you get?
> > >
> > > Excellent! Just need some documentation and then /dev/null can go
> > > to itself ;-)
> >
> > So, let's
> >
> > Bug 1001466 > /dev/null
^^^^^^^^^^^^^^^^^^^^^^^
Excuse my '... > /dev/null' jargon:
http://en.wikipedia.org/wiki//dev/null
> Please change bug's state only when there is some doc about the trick
> you used, and that doc uses the term '/dev/null': this will avoid
> losing time to some other users if they are looking for a solution to
> the absence of /dev/null in eCos.
Good approach. I'll change the state to 'NEED INFO'.
As for my guess and test in GDB. I decided to check that example when I
saw in ecos.ecc:
cdl_option CYGDAT_LIBC_STDIO_DEFAULT_CONSOLE {
# Default value: CYGDAT_IO_SERIAL_TTY_CONSOLE ?
CYGDAT_IO_SERIAL_TTY_CONSOLE : "\"/dev/null\""
}
Hm, /dev/null? And I was looking for what will happen then.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.