From: "Mark A. Greer" <mgreer@mvista.com>
To: Neil Wilson <NWILSON@Airspan.com>,
"'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Sandpoint 3 + MPC7450 + HHL2
Date: Thu, 28 Jun 2001 10:13:03 -0700 [thread overview]
Message-ID: <3B3B659F.ADE63ED0@mvista.com> (raw)
In-Reply-To: 3B3B634F.E6B9FBFC@mvista.com
BTW, what tree are you basing your code off of?
--
"Mark A. Greer" wrote:
> Neil Wilson wrote:
>
> > Got it working now....
> >
> > Not sure if these fixes are just Sandpoint3 or MPC7450 or the combination,
> > but...
> >
> > 1) The openpic_init call in sandpoint_init_IRQ needs the offset argument to
> > get the SIO int setup.
>
> Are you sure you want to do this??? The intsenses stuff in sandpoint_setup.c
> is the way it is for a very good reason. Can you send me your patch so I can
> take a look? Also, can you send the switch settings that you are using.
>
> > 2) I also needed to add a enable of the TBEN in HID0 (bit 0x04000000) just
> > to get the kernel to think about booting at all - I put this in the
> > decompress_kernel function.
>
> I think that your sandpoint-specific boot head.S or somewhere else like that
> would be a much better choice than the ppc-generic decompress_kernel routine.
>
> > Do these sort of changes need pushing into the source tree ?, and if so
> > would anyone care to explain how a newcommer does this, thanks.
>
> Let's hold off on this until people who have sandpoints can take a look.
>
> Mark
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-06-28 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 6:51 Sandpoint 3 + MPC7450 + HHL2 Neil Wilson
2001-06-28 17:03 ` Mark A. Greer
2001-06-28 17:13 ` Mark A. Greer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-29 11:28 Neil Wilson
2001-06-28 20:15 Neil Wilson
2001-06-28 20:06 Neil Wilson
2001-06-27 9:08 Neil Wilson
2001-06-27 16:48 ` Mark A. Greer
2001-06-29 8:14 ` Dan Malek
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=3B3B659F.ADE63ED0@mvista.com \
--to=mgreer@mvista.com \
--cc=NWILSON@Airspan.com \
--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).