From: "Ruslan V.Pisarev" <jerry@izmiran.rssi.ru>
To: Pete Popov <ppopov@embeddedalley.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re[2]: au1200 status
Date: Fri, 20 May 2005 12:20:59 +0300 [thread overview]
Message-ID: <17280353.20050520122059@wicomtechnologies.com> (raw)
In-Reply-To: <1116341942.5802.15.camel@localhost.localdomain>
>[In reply to "au1200 status" from Pete Popov <ppopov@embeddedalley.com> to Ruslan V.Pisarev <jerry@izmiran.rssi.ru> 17/05/2005 17:59]
PP> The Au1200 support will from migrate from 2.4 to 2.6 when either someone
PP> funds the effort or someone has time to do it for fun.
A few thoughts in addition.. At my point of view, au1200 support is
a big mess now. Some companies (AMD, Montawisra, etc) released their
kernels which are not fully synch-ed nor with 2.4 tree at linux-mips
nor with 2.6 one nor with each other. Therefore we forced to "sit and
stay" on one of these old and undeveloped projects (especially most of
them are commercial product (I think even if we'll need a good stable
commercial product - we buy windows :)) or do the same job - make this
all creepy stuff to work on last released kernel. (which will be
replaced after some months with analoguis but better one from amd,
mwista, mr.Jones, mrs.Addams, etc..)
Have you any ideas about this?
()_()
--( ^,^ )---[21398845]- -<The Bat! 3.0.1.33>- -<20/05/2005 11:42>-
(") (")
next prev parent reply other threads:[~2005-05-20 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 11:22 au1200 status Ruslan V.Pisarev
2005-05-17 14:59 ` Pete Popov
2005-05-20 7:36 ` Re[2]: " Ruslan V.Pisarev
2005-05-20 9:20 ` Ruslan V.Pisarev [this message]
2005-05-20 14:37 ` 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=17280353.20050520122059@wicomtechnologies.com \
--to=jerry@izmiran.rssi.ru \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@embeddedalley.com \
/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