From: Pete Popov <ppopov@embeddedalley.com>
To: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Au1x 2.6 updates
Date: Mon, 11 Oct 2004 01:56:07 -0700 [thread overview]
Message-ID: <416A4AA7.4010002@embeddedalley.com> (raw)
I've pushed in a large number of 2.6 patches for the Au1x. The Db1500 is
now very usable and almost completely up to date, including pci, pcmcia,
usb host, audio (oss), and mtd. The rest of the Db1x boards will follow.
There are a few patches in my directory that are needed, until Ralf
approves them and applies them. The directory is
ftp.linux-mips.org:/pub/linux/mips/people/ppopov/2.6. The 36 bit patch
is mandatory; the ide patch is nice but not mandatory; the zImage is
also optional; the pcmcia patch is mandatory if you're going to use pcmcia.
I'll apply the pcmcia patch after some additional testing and then get
rid of the patch. The driver now does not require the 64bit pcmcia patch
that was hard to get accepted in the community tree. The patch uses the
current fixup_bigphys_addr() mechanism, which was already in place
anyway. Thanks to Matt Porter for the simple but brilliant suggestion :)
Let me know if you find any problems.
Thanks,
Pete Popov
Embedded Alley Solutions, Inc
ppopov@embeddedalley.com
reply other threads:[~2004-10-11 8:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=416A4AA7.4010002@embeddedalley.com \
--to=ppopov@embeddedalley.com \
--cc=linux-mips@linux-mips.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