Re: Interrupt handling for RISCV

2017-06-12 Thread Denis Obrezkov
2017-06-11 23:39 GMT+03:00 Hesham Almatary : > On Mon, Jun 12, 2017 at 6:01 AM, Denis Obrezkov > wrote: > > 2017-06-11 22:43 GMT+03:00 Hesham Almatary : > >> > >> Hi Denis, > >> > >> > >> > >> On Sun, Jun 11, 2017 at 11:52 PM, Denis Obrezkov > >> wrote: > >> > Hello Hesham, > >> > > >> > I found

Re: Interrupt handling for RISCV

2017-06-11 Thread Hesham Almatary
On Mon, Jun 12, 2017 at 6:01 AM, Denis Obrezkov wrote: > 2017-06-11 22:43 GMT+03:00 Hesham Almatary : >> >> Hi Denis, >> >> >> >> On Sun, Jun 11, 2017 at 11:52 PM, Denis Obrezkov >> wrote: >> > Hello Hesham, >> > >> > I found out that your code in interrupt handling routine is outdated - >> Which

Re: Interrupt handling for RISCV

2017-06-11 Thread Denis Obrezkov
2017-06-11 22:43 GMT+03:00 Hesham Almatary : > Hi Denis, > > > > On Sun, Jun 11, 2017 at 11:52 PM, Denis Obrezkov > wrote: > > Hello Hesham, > > > > I found out that your code in interrupt handling routine is outdated - > Which interrupt handling routine? The port doesn't handle interrupts. > The

Re: Interrupt handling for RISCV

2017-06-11 Thread Hesham Almatary
Hi Denis, On Sun, Jun 11, 2017 at 11:52 PM, Denis Obrezkov wrote: > Hello Hesham, > > I found out that your code in interrupt handling routine is outdated - Which interrupt handling routine? The port doesn't handle interrupts. The only relevant code is enable/disable interrupts, but it doesn't

Interrupt handling for RISCV

2017-06-11 Thread Denis Obrezkov
Hello Hesham, I found out that your code in interrupt handling routine is outdated - the format of mstatus and sstatus registers was changed. I can produce some patches in a few days, though, I still don't understand how to deal with local and global interrupts. -- Regards, Denis Obrezkov __