linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Cox <adrian@humboldt.co.uk>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 2.6 kernel on Sandpoint
Date: Fri, 12 Mar 2004 09:35:21 +0000	[thread overview]
Message-ID: <1079084120.691.16.camel@newt> (raw)


Has anybody run the linuxppc_2_5 tree on a Sandpoint recently?

I've got a Sandpoint X2. I've ported linuxppc_2_4_devel to run on it,
and the patch is extremely small. My attempt to do the same thing with
linuxppc_2_5 has run into a problem:

Once init opens the console device, the serial driver unmasks irq 4. At
this point irq 4 is permanently asserted, even though the interrupt
register in the UART claims that there is no interrupt.

This should be the same on both X2 and X3 Sandpoints, leaving me curious
as to whether the X3 works with the current tree.

- Adrian Cox
http://www.humboldt.co.uk/


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

             reply	other threads:[~2004-03-12  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12  9:35 Adrian Cox [this message]
2004-03-12 15:23 ` 2.6 kernel on Sandpoint Dan Malek
2004-03-12 17:33   ` Adrian Cox
2004-03-12 17:59     ` Adrian Cox

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=1079084120.691.16.camel@newt \
    --to=adrian@humboldt.co.uk \
    --cc=linuxppc-embedded@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 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).