All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: Linux on Sun e10k
Date: Thu, 22 Feb 2007 11:09:55 +0000	[thread overview]
Message-ID: <20070222.030955.78715327.davem@davemloft.net> (raw)
In-Reply-To: <1169241607.30406.19.camel@duo.jes.ee>

From: Peter Jones <pjones@redhat.com>
Date: Wed, 21 Feb 2007 11:01:49 -0500

> (apologies if you get this more than once; apparently I've been having
> some email trouble)
> 
> On Mon, 2007-01-29 at 09:34 -0800, David Miller wrote:
> 
> > Another oddity is that the buffers are filled at the tail.  So, for
> > example if you have 16 characters to output, you copy them to the
> > final 16-bytes of the buffer area (right before the 2-byte count)
> > and then you write the count to be 16.
> 
> Is the buffer actually filled backwards, or merely aligned to the tail?

The first byte of your console output goes SIZE bytes before the
tail, the last byte goes at the tail.

> > The control register contains either zero (means nothing to do)
> > or another value which indicates certain events have occurred,
> > you poll this when you poll for console input.  The possible
> > values are:
> > 
> > 0	nothing
> > 1	Stop-A break sequence
> > 2	SSP hung up on us and disconnected
> > 3	Console switch to network, stop posting output bytes to SRAM
> > 4	Console switch to SRAM, resume posting output bytes to SRAM
> > 5	Console via network closed
> > 
> > Ignore values 3, 4, and 5 for now, there is a way to redirect console
> > output over the network with the SSP but we'll not support that yet.
> 
> Are 3, 4, and 5 messages from the kernel to the SSP?  If so, don't we
> want to set 4 (and wait for it to clear?) on port->startup() ?

I have no idea, sorry.  Probably they are initiated by a daemon
or similar in userspace under Solaris.  I never checked the details.



      parent reply	other threads:[~2007-02-22 11:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 21:20 Linux on Sun e10k Tõnu Samuel
2007-01-21 15:25 ` Meelis Roos
2007-01-26 22:05 ` Tom 'spot' Callaway
2007-01-26 22:15 ` Tom 'spot' Callaway
2007-01-26 23:12 ` Jan Engelhardt
2007-01-26 23:17 ` Tom 'spot' Callaway
2007-01-27  0:39 ` Tom 'spot' Callaway
2007-01-27  2:10 ` David Miller
2007-01-27  3:42 ` Tom 'spot' Callaway
2007-01-27  4:28 ` Tom 'spot' Callaway
2007-01-27 10:19 ` Tõnu Samuel
2007-01-27 11:17 ` Jan Engelhardt
2007-01-27 15:37 ` Tom 'spot' Callaway
2007-01-27 16:05 ` Jan Engelhardt
2007-01-27 16:31 ` Tom 'spot' Callaway
2007-01-27 16:53 ` Jan Engelhardt
2007-01-28  2:38 ` David Miller
2007-01-28 12:26 ` Jan Engelhardt
2007-01-29 15:08 ` Meelis Roos
2007-01-29 16:39 ` David Miller
2007-01-29 16:52 ` Tom 'spot' Callaway
2007-01-29 17:34 ` David Miller
2007-01-29 19:45 ` Tom 'spot' Callaway
2007-01-29 20:07 ` David Miller
2007-02-21 16:01 ` Peter Jones
2007-02-22 11:09 ` David Miller [this message]

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=20070222.030955.78715327.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=sparclinux@vger.kernel.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.