public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: srinivas srungaram <sskumar341@krify.com>
To: obiwanthejediknight@worldnet.att.net, Linux-8086@Vger.Kernel.Org
Subject: RE: ELKS porting to DSP
Date: Fri, 26 Sep 2003 22:44:14 -0700 (PDT)	[thread overview]
Message-ID: <20030927054415.0B01272A0@sitemail.everyone.net> (raw)

Hello Gregg C Levine and   ALL !
 
I and my colleage only  discussed this topic , 3 months earlier.
Now I am on  this  project...
So can u tell me  which parts of the code need to be changed.I want to have minimal code to be booted first and later want to add one by one.
 
I want to make  minimum kernel  Image and bootit from the DSP . This is my first aim.
Thinking in this way Plz ,  suggest me the directories  wise  changes( like   kernel /     , fs ,   /  arch/i86/kernel/      , arch/i86/mm/  ).  
 
I am facing problems  to understand all the code as i am new to this field.
Please Help  me,
 
Thanks and Regards
Srinivas 
 
-----Original Message----- 
From: Gregg C Levine [mailto:obiwanthejediknight@worldnet.att.net] 
Sent: Fri 9/26/2003 9:16 PM 
To: Srinivasa Kumar Srungaram; Linux-8086@Vger.Kernel.Org 
Cc: 
Subject: Re: ELKS porting to DSP


Hello from Gregg C Levine
Everything. ELKS is a x86 targeted project. As it happens, ELKS can not be
ported to that DSP with out major work. You are strongly suggested to
contact the company that makes the chip regarding a more suitable Real Time
kernel. Also please examine the archives of this group, as we went over this
subject, three times much earlier.
Gregg C Levine obiwanthejediknight@att.net
<This signature will be replaced, pending an approval from the Jedi Council.
>
----- Original Message -----
From: "srinivas srungaram" <sskumar341@krify.com>
To: <Linux-8086@Vger.Kernel.Org>
Sent: Wednesday, September 24, 2003 11:20 PM
Subject: ELKS porting to DSP


> Hellow all !
>
> I am trying  to port elks on to Blackfin DSP (21535).
> I took the working sources form  the elks site which  worked   on  my 86
machine.
>
> Can any one suggest me  what are the exact  issuues  (problems) that
comes into picture while porting.
> i.e I want to know which parts of the  code need to changed......
>
> My present status of this project :
>          I  compiled the C sources  of elks with Blackfin compiler
commenting out assembly part and trying to
>             port..
>
> Srinivas
>
>
> _____________________________________________________________
> I use Krify Mail - http://mail.krify.com  Get  Yourname at  Krify today!
> -
> 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




_____________________________________________________________
I use Krify Mail - http://mail.krify.com  Get  Yourname at  Krify today!

             reply	other threads:[~2003-09-27  5:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-27  5:44 srinivas srungaram [this message]
2003-09-27 14:39 ` ELKS porting to DSP Gregg C Levine
2003-09-27 16:03   ` Harry Kalogirou
2003-09-29  0:55     ` Syed Faisal Akber
  -- strict thread matches above, loose matches on Subject: below --
2003-09-25  3:20 srinivas srungaram
2003-09-26 15:46 ` Gregg C Levine

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=20030927054415.0B01272A0@sitemail.everyone.net \
    --to=sskumar341@krify.com \
    --cc=Linux-8086@Vger.Kernel.Org \
    --cc=obiwanthejediknight@worldnet.att.net \
    --cc=srinivasa.srungaram@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