All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jamie Heilman <jamie@audible.transient.net>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: BriQ & Linux 2.6
Date: Sat, 22 May 2004 14:14:00 +1000	[thread overview]
Message-ID: <1085199239.9230.4.camel@gaston> (raw)
In-Reply-To: <20040521233523.GJ8520@audible.transient.net>


On Sat, 2004-05-22 at 09:35, Jamie Heilman wrote:
> Benjamin Herrenschmidt wrote:
> > I have a few patches for the briq, I didn't push them upstream yet,
> > as I'm trying to find a clean way to deal with an issue relative
> > to the serial port clock setting.
>
> What is that issue out of curriosity?  I ask because... well I've had
> some rather incongruous experinences with serial on the BriQ compared
> to what Karsten at Total Impact was telling me I should be having.

Well... the base clock isn't what the driver thinks, so it must be
hacked. But the driver doesn't provide a clean way to set another
base clock, I'm trying to find something better than what the hack
in the patch does.

> Basically, all the kernels they've shipped recently had code that did
> some funky stuff to the baud rate.  On my briq that made the serial
> port spew total garbage during boot until init hits runlevel 2 and
> resets it (debian), then everything is OK again.  After reverting their
> changes everything works again.  So I'm afraid I've had to take their
> code with a grain of salt.  ISTR they were multiplying something by 4
> that I found was better left alone... but I'd have to go back and see
> if I could find my old source trees to be sure, last time I looked at
> this box was 2 years ago.
>
> > Enclosed is my latest version of that patch (may need some hand-applying
> > as it's a couple of monthes old).
>
> Thanks!  I'll play with it.
>
> --
> Jamie Heilman                     http://audible.transient.net/~jamie/
> "I was in love once -- a Sinclair ZX-81.  People said, "No, Holly,
>  she's not for you." She was cheap, she was stupid and she wouldn't
>  load -- well, not for me, anyway."                     -Holly
>
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-05-22  4:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-21  7:40 BriQ & Linux 2.6 Jamie Heilman
2004-05-21 23:10 ` Benjamin Herrenschmidt
2004-05-21 23:35   ` Jamie Heilman
2004-05-22  4:14     ` Benjamin Herrenschmidt [this message]
2004-05-22  6:45       ` Jamie Heilman
2004-05-22  7:12         ` Benjamin Herrenschmidt
2004-05-22 19:36           ` Jamie Heilman
2004-05-24  6:47             ` Jamie Heilman
2004-05-25 23:30         ` Benjamin Herrenschmidt
2004-05-26  0:00           ` Jamie Heilman

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=1085199239.9230.4.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=jamie@audible.transient.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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.