From: Matthieu CASTET <castet.matthieu@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: ADI Blackfin patch for kernel 2.6.14
Date: Tue, 15 Nov 2005 20:11:52 +0100 [thread overview]
Message-ID: <pan.2005.11.15.19.11.50.359544@free.fr> (raw)
In-Reply-To: <6.1.1.1.0.20051114132644.01ec1170@ptg1.spd.analog.com>
Hi,
Le Mon, 14 Nov 2005 15:53:42 -0500, Robin Getz a écrit :
> Andrew wrote:
> Since you asked - The Blackfin Processor includes the common 4 processor Ps
> that people request for embedded designs - price, power, performance &
> penguins.
Could I add that ADI chips may be are cheap, but the implementation for
that could be ugly.
For example for the usb eagle (adsl chip) developped by ADI, they put the
smallest RAM as possible on the board. For that reason the DSP firmware is
swapped on the host computer : the firmware is split in pages and when the
chip wants a new page it asks it via an interrupt and the host sends the
requested page...
Also ADI never cares to correct some bugs in the usb eagle firmware nor to
sent us a correct documentation (after 6 months of discusion, they sent us
a 3 years old documentation and they never agree to put a
license for the firmware).
Finaly most of the linux code from ADI that I saw in my eagle usb projects
and in my job weren't very Linux compliant/robust (the first version of
eagle usb driver made by ADI had a memleack that make the modem unsuable
after some hours of use) [1].
I know there are different teams at Analog device and blackfin guys aren't
related to these projects.
I hope backfin project will change my vision of ADI ;)
Matthieu
[1] we have a joke about that : (in french) Là où ADI passe, les
standards trépassent.
next prev parent reply other threads:[~2005-11-15 19:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 20:53 Robin Getz
2005-11-15 19:11 ` Matthieu CASTET [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-17 5:38 Robin Getz
2005-11-01 9:28 Luke Yang
2005-11-01 16:51 ` Adrian Bunk
2005-11-02 7:06 ` Luke Yang
2005-11-04 4:59 ` Luke Yang
2005-11-04 23:06 ` Greg KH
2005-11-07 6:58 ` Luke Yang
2005-11-07 16:59 ` Greg KH
2005-11-08 7:50 ` Andrew Morton
2005-11-11 11:26 ` Luke Yang
2005-11-12 11:58 ` Andrey Volkov
2005-11-14 7:22 ` Luke Yang
2005-11-12 21:47 ` Greg KH
2005-11-13 14:22 ` Bernd Schmidt
2005-11-14 7:34 ` Luke Yang
2005-11-14 7:52 ` Arjan van de Ven
2005-11-15 2:40 ` Luke Yang
2005-11-15 4:14 ` Greg KH
2005-11-14 12:53 ` Alan Cox
2005-11-16 3:44 ` Luke Yang
2005-11-16 6:11 ` Paul Jackson
2005-11-16 6:34 ` Luke Yang
2005-11-16 13:42 ` Bernd Schmidt
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=pan.2005.11.15.19.11.50.359544@free.fr \
--to=castet.matthieu@free.fr \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®