public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "Raghavan" <raghavan.viswanathan@wipro.com>
To: Syed Faisal Akber <faisal.akber@utoronto.ca>
Cc: Linux-8086@Vger.Kernel.Org
Subject: Re: Porting ELKS
Date: Tue, 22 Jul 2003 11:42:10 +0530	[thread overview]
Message-ID: <023201c35018$2f68a450$8c06770a@wipro.com> (raw)
In-Reply-To: Pine.GSO.4.44.0307211235270.26077-100000@SERVER1.AKBER.NET

Fasal,

Thanks very much for the reply.

If I understand you correctly, we "can" have a port of ELKS as is without
change in Memory model , but it
will possibly be pedestrian.

I took a look at eCOS , but it looks like a nice full fledged OS with
excellent features. Porting it might be
a difficult task might be like an Year or so ...

I am inclined towards ELKS because I can possibly have a port like in 3 to 4
months ...
My priority is really to have applications running on Blackfin ASAP.

Also, why do we need to have gcc ported ?
Cant I use the native compiler provided by ADI guys for the Blackfin
Processor ?
Yeah..I need to tweak the compiler options to the respective equivalents on
Blackfin Compiler ..; I am not seeing anything else ...
Am I missing something ?

Am I looking too optimistic to assume a 'as is' port of ELKS to Blackfin
in 3 to 4 months ? I was thinking of taking Memory management after I have a
'working' version of  ELKS ...

Does this sound reasonable ?

Bye,
Raghavan V

----- Original Message -----
From: "Syed Faisal Akber" <faisal.akber@utoronto.ca>
To: "Raghavan" <raghavan.viswanathan@wipro.com>
Cc: <Linux-8086@Vger.Kernel.Org>
Sent: Monday, July 21, 2003 10:18 PM
Subject: Re: Porting ELKS


> Porting ELKS to Blackfin would be a complete and total rewrite of the
> memory management.  The segmented memory model doesn't suit the Blackfin
> processor well and would probably degrade the performance on that
> processor.
>
> eCOS is POSIX compliant.
>
> On Mon, 21 Jul 2003, Raghavan wrote:
>
> >
> > Are you saying ELKS would be inefficient on the DSP Processor ..or is it
> > that porting ELKS on Blackfin be like a total rewrite ?
>
>
> >
> > Is eCOS port feasible like say in a 3-4 months time frame ? Is eCOS
POSIX
> > compliant ..so that we can get any application compile & run on it
easily ?
> >
> > Bye,
> > Raghavan V
> >
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "Syed Faisal Akber" <faisal.akber@utoronto.ca>
> > To: "Raghavan" <raghavan.viswanathan@wipro.com>
> > Cc: <Linux-8086@Vger.Kernel.Org>
> > Sent: Monday, July 21, 2003 1:12 AM
> > Subject: Re: Porting ELKS
> >
> >
> > > 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
> > > >
> > >
> >
> > -
> > 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
> >
>


  reply	other threads:[~2003-07-22  6:12 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
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 [this message]
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='023201c35018$2f68a450$8c06770a@wipro.com' \
    --to=raghavan.viswanathan@wipro.com \
    --cc=Linux-8086@Vger.Kernel.Org \
    --cc=faisal.akber@utoronto.ca \
    /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