From: Andreas Oberritter <obi@saftware.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: new code for an mpc8xx board (dbox2)
Date: 03 Aug 2003 04:42:09 +0200 [thread overview]
Message-ID: <1059878529.665.50.camel@localhost> (raw)
Hi,
I'd like to get support for the dbox2, which is a DVB receiver with an
mpc823 cpu, into the linux kernel, to make it bootable without
further patching. Since I am new to submitting kernel patches, I don't
know who to ask best for inclusion. Benjamin Herrenschmidt pointed me to
this mailing list.
On which kernel tree shall patches be based to get into vanilla 2.4?
The current patchset against linux-2.4.22-pre6 can be viewed via webcvs
at http://cvs.tuxbox.org/cgi-bin/viewcvs.cgi/tuxbox/cdk/Patches/
I will create a new set as soon as I know which tree to use best.
I'd also like to know if there is a better way to handle edge triggered
interrupts on 8xx than it is done in
linux-2.4.22-pre6-dbox2-irq.diff. Should CONFIG_DBOX2 be removed in this
patch or maybe replaced by CONFIG_8xx?
I think linux-2.4.22-pre6-dbox2-board.diff is a trivial patch and will
not offend any other boards.
linux-2.4.22-pre6-dbox2-watchdog.diff is needed because the
bootloader of this board enables the watchdog. Since it is a generic
implementation for handling an 8xx watchdog, I'd add CONFIG_8xx_WATCHDOG
for it instead of CONFIG_DBOX2, if no one complains.
Regards,
Andreas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-08-03 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 2:42 Andreas Oberritter [this message]
2003-08-04 17:24 ` new code for an mpc8xx board (dbox2) Tom Rini
2003-08-04 21:36 ` Florian Schirmer
2003-08-04 23:12 ` Tom Rini
2003-08-18 18:02 ` Tom Rini
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=1059878529.665.50.camel@localhost \
--to=obi@saftware.de \
--cc=linuxppc-dev@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).