From: "Sébastien Chrétien" <sebastien.chretien.enseirb@gmail.com>
To: benh@kernel.crashing.org
Cc: "Sébastien CHRETIEN" <sebastien.chretien@fr.thalesgroup.com>,
linuxppc-dev@ozlabs.org, "Jenkins,
Clive" <Clive.Jenkins@xerox.com>
Subject: Re: Trace
Date: Tue, 2 Sep 2008 09:34:39 +0200 [thread overview]
Message-ID: <319b0ac50809020034m12b4d57cj1fdf31f3282935e6@mail.gmail.com> (raw)
In-Reply-To: <1220334314.13010.89.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
ok is it a bad way to write a tty driver ? why ?
2008/9/2, Benjamin Herrenschmidt <benh@kernel.crashing.org>:
>
> On Tue, 2008-09-02 at 07:13 +0200, Sébastien CHRETIEN wrote:
> > My board has only a uart device on a FPGA. I don't use the serial layer
> > because it isn't documented in Linux Device Driver 3rd. Only the tty
> > layer is documented
>
>
> You won't go very far in linux kernel dev. with using books like
> that :-)
>
> Look at other drivers in drivers/serial that should give you all the
> information you need :-0
>
> Cheers,
> Ben.
>
>
>
[-- Attachment #2: Type: text/html, Size: 865 bytes --]
next prev parent reply other threads:[~2008-09-02 7:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 9:16 Trace Sébastien Chrétien
2008-09-01 9:23 ` Trace Benjamin Herrenschmidt
2008-09-01 10:00 ` Trace Jenkins, Clive
2008-09-01 12:25 ` Trace Sébastien Chrétien
2008-09-01 13:54 ` Trace Jenkins, Clive
2008-09-01 13:58 ` Trace Jenkins, Clive
2008-09-01 16:33 ` Trace Sébastien Chrétien
2008-09-02 0:13 ` Trace Benjamin Herrenschmidt
2008-09-02 5:13 ` Trace Sébastien CHRETIEN
2008-09-02 5:45 ` Trace Benjamin Herrenschmidt
2008-09-02 7:34 ` Sébastien Chrétien [this message]
2008-09-02 8:19 ` Trace Benjamin Herrenschmidt
2008-09-02 8:44 ` Trace Sébastien Chrétien
2008-09-04 20:19 ` Trace Sébastien Chrétien
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=319b0ac50809020034m12b4d57cj1fdf31f3282935e6@mail.gmail.com \
--to=sebastien.chretien.enseirb@gmail.com \
--cc=Clive.Jenkins@xerox.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sebastien.chretien@fr.thalesgroup.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 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 NNTP newsgroup(s).