All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien Chrétien" <sebastien.chretien.enseirb@gmail.com>
To: benh@kernel.crashing.org
Cc: "Sébastien Chrétien" <sebastien.chretien.enseirb@gmail.com>,
	"Jenkins, Clive" <Clive.Jenkins@xerox.com>,
	linuxppc-dev@ozlabs.org,
	EN <sebastien.chretien@fr.thalesgroup.com>
Subject: Re: Trace
Date: Thu, 04 Sep 2008 22:19:19 +0200	[thread overview]
Message-ID: <48C042C7.4090900@gmail.com> (raw)
In-Reply-To: <1220343590.13010.118.camel@pasglop>


I followed your advice : I used the UART layer.
It is easier.
Thanks


Benjamin Herrenschmidt a écrit :
> On Tue, 2008-09-02 at 09:34 +0200, Sébastien Chrétien wrote:
>   
>> ok is it a bad way to write a tty driver ? why ?
>>     
>
> Not necessarily, it's just overkill. The UART layer handles a lot
> of stuff for you. The tty layer is tricky to get right.
>
> Cheers,
> Ben.
>
>
>   

  parent reply	other threads:[~2008-09-04 20:20 UTC|newest]

Thread overview: 15+ 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                 ` Trace Sébastien Chrétien
2008-09-02  8:19                   ` Trace Benjamin Herrenschmidt
2008-09-02  8:44                     ` Trace Sébastien Chrétien
2008-09-04 20:19                     ` Sébastien Chrétien [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-13 18:14 TRACE Moritz Gartenmeister

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=48C042C7.4090900@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 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.