From: Sylvain Munaut <tnt@246tnt.com>
To: Dan Malek <dan@embeddededge.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Linux 2.6 on AMD Alchemy Au1500
Date: Wed, 28 Jan 2004 16:15:31 +0100 [thread overview]
Message-ID: <4017D213.8070108@246tNt.com> (raw)
In-Reply-To: <4017CF37.4070708@embeddededge.com>
Dan Malek wrote:
>> For a new design, we're considering Alchemy Au1500 processor family.
>> I'd like to know what is the current state of the linux 2.6 on this
>> platforms / experiences ?
>
>
> There are several of us working on it. The kernel is basically
> functional,
> and we are now in the midst of the 36-bit addressing updates for the
> peripherals, such as PCI. This should be completed soon.
>
Ok cool.
>> I mainly need :
>> - PCI support to connect Wifi, IDE controller, USB2.0 Host, FireWire
>> controller
>> - Included Ethernet support
>
>
> If you are looking for product support, you should probably be contacting
> people that provide these services :-) We will eventually get around to
> testing all of these devices, but those of us working on this are likely
> to have different priorities.
Yes, what I meant is that I needed PCI support and wanted to know if it
was OK, the chips I connect on it are supported.
I just forgot to ask if the AC97 stuff was already supported by the ALSA
stuff in the kernel ?
Thanks for the info
Munaut Sylvain
next prev parent reply other threads:[~2004-01-28 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 10:44 Linux 2.6 on AMD Alchemy Au1500 Sylvain Munaut
2004-01-28 15:03 ` Dan Malek
2004-01-28 15:15 ` Sylvain Munaut [this message]
2004-01-28 15:05 ` Pete Popov
2004-01-28 15:18 ` Sylvain Munaut
2004-01-28 15:22 ` Pete Popov
2004-01-28 15:36 ` Ralf Baechle
2004-01-28 15:46 ` Sylvain Munaut
2004-01-28 15:46 ` Sylvain Munaut
2004-01-28 15:57 ` 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=4017D213.8070108@246tNt.com \
--to=tnt@246tnt.com \
--cc=dan@embeddededge.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