From: "Tom 'spot' Callaway" <tcallawa@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: Linux on Sun e10k
Date: Mon, 29 Jan 2007 16:52:40 +0000 [thread overview]
Message-ID: <1170089560.25368.38.camel@localhost.localdomain> (raw)
In-Reply-To: <1169241607.30406.19.camel@duo.jes.ee>
On Mon, 2007-01-29 at 17:08 +0200, Meelis Roos wrote:
> > Adding proper support for the e10K console would be a nice
> > easy sparc64 kernel project for someone who wants to get
> > involved and has access to such a machine.
>
> Are the any specs available, or is it just reverse engineering?
This is the question I'd really like to hear the answer to. I can't find
anything at all, either in the Sun docs or in the Internet tubes.
The prom console seems to work to a point, up until the kernel oopses. I
don't know what more to do to debug that oops, the VM is a bit of a
black box to me.
~spot
next prev parent reply other threads:[~2007-01-29 16:52 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 [this message]
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
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=1170089560.25368.38.camel@localhost.localdomain \
--to=tcallawa@redhat.com \
--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.