All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@domain.hid>
To: toon.diels@domain.hid
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] porting adeos to MIPS architecture
Date: Wed, 17 Jul 2002 12:41:37 -0400	[thread overview]
Message-ID: <3D359E41.91626167@domain.hid> (raw)
In-Reply-To: OFCD857115.70858C2E-ONC1256BF9.004147F0@domain.hid

Hello Toon,

This is great. I'm looking forward to more ports like this. I'd really
like to take a look at the drawings and give you some feedback, but
there's no Visio for Linux and I haven't been running that other OS
for a long time. Could you export those to PS or EPS?

Cheers,

Karim

toon.diels@domain.hid wrote:
> 
> Hi all,
> 
> I am porting adeos-1.0 to a MIPS processor. The most straight forward activities are porting the inline
> assembly code for eg enabling/disabling interrupt, save/restoring registers etc.
> 
> However, porting the interrupt pipe (and domain switching) is not that trivial since it requires rewriting of the ipipe.
> MIPS interrupt mechanisms are different then the x86 interrupt handling.
> 
> Before I start rewriting the interrupt (and exception) pipe mechanism to MIPS architecture, I would like to ask the
> ADEOS originators what they expect to be reused when doing an architecture port: eg is it just reusing the API or
> do you also want to reuse the sources (and which ones).
> 
> I have added some visio drawings with respect to the MIPS interrupt/exception handling to indicate how this takes
> place on a MIPS.
> 
> (See attached file: viper_irq_pipeline.vsd)(See attached file: viper_irq.vsd)
> 
> thank you for the information and kind regards,
> 
> Toon
> 
>   ------------------------------------------------------------------------------------------------------------------------------------------------------
>                              Name: viper_irq_pipeline.vsd
>    viper_irq_pipeline.vsd    Type: unspecified type (application/octet-stream)
>                          Encoding: base64
> 
>                     Name: viper_irq.vsd
>    viper_irq.vsd    Type: unspecified type (application/octet-stream)
>                 Encoding: base64

-- 
===================================================
                 Karim Yaghmour
               karim@domain.hid
      Embedded and Real-Time Linux Expert
===================================================


  parent reply	other threads:[~2002-07-17 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 12:03 [Adeos-main] porting adeos to MIPS architecture toon.diels
2002-07-17 13:17 ` [Adeos-main] " Philippe Gerum
2002-07-17 16:41 ` Karim Yaghmour [this message]
2002-07-18  6:40 ` [Adeos-main] " Herman Bruyninckx

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=3D359E41.91626167@domain.hid \
    --to=karim@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=toon.diels@domain.hid \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.