From: Syed Faisal Akber <faisal.akber@utoronto.ca>
To: Raghavan <raghavan.viswanathan@wipro.com>
Cc: Linux-8086@Vger.Kernel.Org
Subject: Re: Porting ELKS
Date: Sun, 20 Jul 2003 15:42:20 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.44.0307201537440.25099-100000@SERVER1.AKBER.NET> (raw)
In-Reply-To: <044401c34d1b$5d6f3210$8c06770a@wipro.com>
Hi Raghavan,
I think that porting ELKS to the Blackfin is a waste of time. ELKS is
written to take advantage of 8086 processor quirks. The Blackfin (or MSA)
architecture is quite a bit different.
(1) The Blackfin does not have an TLB based MMU. You cannot use Linux,
but you can use uClinux. ELKS is similar to uClinux but the memory models
are very different.
(2) You may want to start using uClinux. There already exists a port for
Blackfin. You will probably have to contact Analog Devices to get more
information regarding this.
Regards,
Faisal
On Fri, 18 Jul 2003, Raghavan wrote:
> Hi,
>
> I am intending to port ELKS on to Analog Devices's Blackfin DSP Processor.
>
> I am having a couple of questions
>
> (1) Does ELKS take advantage of the MMU facility of the x86 Systems ?. I ask
> this because the Blackfin does not.
>
> (2) What would be a good strategy to start the porting exercise ? Any
> previous porting lessons would help.
>
> Bye,
> Raghavan V
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2003-07-20 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 10:57 Porting ELKS Raghavan
2003-07-19 20:12 ` Alan Cox
2003-07-20 19:42 ` Syed Faisal Akber [this message]
2003-07-21 5:09 ` Raghavan
2003-07-21 6:22 ` Riley Williams
2003-07-21 16:49 ` Syed Faisal Akber
2003-07-21 16:48 ` Syed Faisal Akber
2003-07-22 6:12 ` Raghavan
2003-07-29 1:56 ` Syed Faisal Akber
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=Pine.GSO.4.44.0307201537440.25099-100000@SERVER1.AKBER.NET \
--to=faisal.akber@utoronto.ca \
--cc=Linux-8086@Vger.Kernel.Org \
--cc=raghavan.viswanathan@wipro.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