linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Pantelis Antoniou <panto@intracom.gr>,
	Kumar Gala <kumar.gala@motorola.com>,
	Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [PATCH] Take two of the new serial uart driver.
Date: Sat, 05 Jun 2004 23:02:09 +0100	[thread overview]
Message-ID: <1086472929.4862.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20040605192221.GT15195@smtp.west.cox.net>


On Sat, 2004-06-05 at 12:22 -0700, Tom Rini wrote:
> On Sat, Jun 05, 2004 at 10:12:24AM +0100, David Woodhouse wrote:
>
> > On Thu, 2004-06-03 at 17:13 +0300, Pantelis Antoniou wrote:
> > > Hi
> > >
> > > The following patch updates the new CPM1/CPM2 uart driver.
> >
> > It seems to lose queued characters from the kernel output when userspace
> > /dev/console is first opened. Should you drain the FIFO before resetting
> > the hardware on open? Or indeed refrain from resetting the hardware if
> > you're not actually changing anything?
>
> I haven't seen this problem on 8xx myself.

8265 here.

VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 100k iné
sh-2.05b#

> > This is with console on ttyCPM0 == SMC1. SysRq is also non-functional.
>
> SysRq is fixed in the linuxppc-2.5 tree now.

There's something weird about the console output if I hit SysRq-B. It's
as if each 32-bit word is rotated by 8 bits before being sent. The oops
I expect -- I know machine_restart() doesn't work and I'll fix if if I
have the toy in question here at home without automatic power control
for any length of time. But I do expect the oops to be readable :)

SysRq : ResettinttihMac inecchenk ir ke nelemodC.
eausyd br (fSom =RR10410 0):nTrarsfer eraor sck aignOl
:opsc maehine ch ck,:sig[ 7
 ... etc...

Also, userspace is broken without panto's _tlbia() hack in
update_mmu_cache().

Btw, someone with shell access to the linuxppc BK tree needs to manually
edit SCCS/s.ChangeSet and fix the checksum on this changeset:

ChangeSet@1.497.3879.2, 2004-04-09 10:55:30-07:00, rvinson@linuxbox.(none)
  Updating Force PCore to 2.6

This should do it:
	perl -pi -e s/K64684/K65408/ SCCS/s.ChangeSet

(for reference, if you 'bk export -tpatch' the offending cset it'll tell
you what the checksum is and what it should be.).

Then 'get ChangeSet' and it'll bitch about the checksum. Edit
SCCS/s.ChangeSet and fix the 'Hxxxxx' checksum in the very first line,
correcting it to the value it just gave you.

--
dwmw2


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

  reply	other threads:[~2004-06-05 22:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 14:13 [PATCH] Take two of the new serial uart driver Pantelis Antoniou
2004-06-03 16:21 ` David Woodhouse
2004-06-04  6:31   ` Pantelis Antoniou
2004-06-05  9:12 ` David Woodhouse
2004-06-05 19:22   ` Tom Rini
2004-06-05 22:02     ` David Woodhouse [this message]
2004-06-06  1:30       ` Tom Rini
2004-06-07  8:11       ` Pantelis Antoniou
2004-06-07  8:36         ` David Woodhouse
2004-06-07  8:34           ` Pantelis Antoniou
2004-06-07  8:53             ` David Woodhouse
2004-06-07  8:53               ` Pantelis Antoniou
2004-06-07  9:06                 ` David Woodhouse
2004-06-07  9:12         ` David Woodhouse

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=1086472929.4862.12.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=kumar.gala@motorola.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=panto@intracom.gr \
    --cc=trini@kernel.crashing.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 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).