From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/06] sh: sh7343 and se7343 patches
Date: Thu, 04 Dec 2008 12:01:12 +0000 [thread overview]
Message-ID: <20081204120112.GA14492@linux-sh.org> (raw)
In-Reply-To: <20081204085946.25773.64257.sendpatchset@rx1.opensource.se>
On Thu, Dec 04, 2008 at 05:59:46PM +0900, Magnus Damm wrote:
> sh7343 and se7343 patches:
>
> [PATCH 01/06] sh: sh7343 scif configuration update
> [PATCH 02/06] sh: fix number of interrupts on se7343
> [PATCH 03/06] sh: add st16c2550 devices to se7343
> [PATCH 04/06] sh: add isp1161 usb host device to se7343
> [PATCH 05/06] sh: remove ioport cruft and smc91x from se7343
> [PATCH 06/06] sh: update se7343 defconfig
>
> This patchset simply updates the sh7343 processor code a bit and
> modifies the se7343 board support code to include the external usb
> host controller chip and on-board uarts. The out-of-date ioport
> code gets removed while at it - including some old support for
> unknown-ne2000-pcmcia-card, cf-over-pcmcia and a mysterical smc91x
> that once must have been on a special daughterboard.
>
> Now with the USB host controller in place we get network connection
> using an ethernet-over-usb adapter (yay) but we're still unfortunately
> stuck loading the kernel over the serial gdbstub which makes kernel
> development too slow to be practical.
>
> Signed-off-by: Magnus Damm <damm@igel.co.jp>
Applied, thanks.
prev parent reply other threads:[~2008-12-04 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 8:59 [PATCH 00/06] sh: sh7343 and se7343 patches Magnus Damm
2008-12-04 12:01 ` Paul Mundt [this message]
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=20081204120112.GA14492@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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.