From: Andreas Oberritter <obi@saftware.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] fix build of ibmstb4 and ibmstbx25
Date: 24 Sep 2003 23:00:07 +0200 [thread overview]
Message-ID: <1064437206.1807.42.camel@shiva.eth.saftware.de> (raw)
In-Reply-To: <20030924171739.GA30820@ip68-0-152-218.tc.ph.cox.net>
On Wed, 2003-09-24 at 19:17, Tom Rini wrote:
> On Wed, Sep 24, 2003 at 05:04:49AM +0200, Andreas Oberritter wrote:
>
> > Hi Tom,
> >
> > config.in.diff adds two missing '$' for config variables in
> > arch/ppc/config.in and the two other patches update the ocp definitions
> > for the stb4xxx and stbx25xx CPUs, so they can be built again. I used
> > linuxppc_2_4_devel, but they are needed for linuxppc-2.4, too.
>
> Applied. Does this mean you have the HW and can test things?
Thanks!
Yes, I have a set-top-box using the stb4500. I don't have an stbx25xx
yet, but there are or will be some interesting boxes on the market using
it.
I found two more bugs in linuxppc-2.4:
ppc405_wdt.c is missing, but it is available as a config option.
embed_config.c contains an #endif below #include <asm/io.h> without a
matching #if.
Unfortunately I can't send patches at the moment because my harddisk
died partially this morning...
Btw, thanks for applying the dbox2 patches! Will the watchdog code be
merged in before 2.4.23, too?
Regards,
Andreas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-24 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 3:04 [PATCH] fix build of ibmstb4 and ibmstbx25 Andreas Oberritter
2003-09-24 17:17 ` Tom Rini
2003-09-24 21:00 ` Andreas Oberritter [this message]
2003-09-24 21:19 ` Matt Porter
2003-09-24 21:32 ` Tom Rini
2003-09-24 21:53 ` Matt Porter
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=1064437206.1807.42.camel@shiva.eth.saftware.de \
--to=obi@saftware.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--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).