From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 11 Oct 2008 19:32:40 +0000 (GMT) From: Gabriele Moabiti MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1318023392-1223753560=:51777" Message-ID: <333188.51777.qm@domain.hid> Subject: Re: [Xenomai-help] trap exceptions in user List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Xenomai help --0-1318023392-1223753560=:51777 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable =0A>Yes, but I still think this is useless. If your user-space code expects= =0A>to be running from 1MB to 16MB, it expects this for virtual addresses,= =0A>not for physical addresses. So, I really think you should mmap the 1MB= =0A>to 16MB region by passing the start address to mmap with the MMAP_FIXED= =0A>flag.=0A=0AI know my way to solve this problem is very strange but ther= e are some reasons.=0AIt is done for compatibility reasons (DMA and a stran= ge architecture with custom gdt entries needed by the asm blob...)=0AIn thi= s application I don't need contiguous physical addresses so I will try the = mmap fixed way.=0AI didn't only want to fork the driver but it is not a big= problem...=0A=0A>You should trace the exception path in the I-pipe patch t= o find the=0A>point where your exception handling callback is not called.= =0A=0Awill it be a large print work or there are another ways to do that? := )=0A=0A Gabriele=0A=0A=0A Scopri il blog di Yahoo! Mail:=0ATrucchi,= novit=C3=A0 e scrivi la tua opinione.=0Ahttp://www.ymailblogit.com/blog --0-1318023392-1223753560=:51777 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

<= br>>Yes, but I still think this is useless. If your user-space code expe= cts
>to be running from 1MB to 16MB, it expects this for virtual addr= esses,
>not for physical addresses. So, I really think you should mma= p the 1MB
>to 16MB region by passing the start address to mmap with t= he MMAP_FIXED
>flag.

I know my way to solve this problem is ve= ry strange but there are some reasons.
It is done for compatibility reas= ons (DMA and a strange architecture with custom gdt entries needed by the a= sm blob...)
In this application I don't need contiguous physical address= es so I will try the mmap fixed way.
I didn't only want to fork the driver but it is not a big problem...

>You should trace the exc= eption path in the I-pipe patch to find the
>point where your excepti= on handling callback is not called.

will it be a large print work or= there are another ways to do that? :)

Gabriele

=0A=0A=0A=0A

Scopri il Blog di Yahoo! Mail: trucchi, novit=C3=A0, consigli... e scrivi la tu= a opinione! --0-1318023392-1223753560=:51777--