Re: [PATCH 4/5] Port am335x usb driver to RTEMS.

2017-06-25 Thread Sichen Zhao
Yes, i will discuss it with my mentor, and do my best. Best Regards Sichen Zhao From: Sebastian Huber Sent: Saturday, June 24, 2017 17:07 To: Sichen Zhao Cc: Sichen Zhao; devel; punitv...@gmail.com; christian mauderer Subject: Re: [PATCH 4/5] Port am335x

Re: RSB Architecture request: aarch64, x86_64, risc-v

2017-06-25 Thread Hesham Almatary
Hi Chris, On Mon, Jun 26, 2017 at 10:11 AM, Chris Johns wrote: > On 26/06/2017 10:03, Hesham Almatary wrote: >> >> I've already submitted a patch for riscv32 here [1]. >> > > Thanks. My reading of the thread there are some unresolved questions. > > What is the status? > Regarding FSF paperwork,

Re: RSB Architecture request: aarch64, x86_64, risc-v

2017-06-25 Thread Chris Johns
On 26/06/2017 10:03, Hesham Almatary wrote: > > I've already submitted a patch for riscv32 here [1]. > Thanks. My reading of the thread there are some unresolved questions. What is the status? Thanks Chris > [1] https://lists.rtems.org/pipermail/devel/2017-May/017951.html.

Re: RSB Architecture request: aarch64, x86_64, risc-v

2017-06-25 Thread Hesham Almatary
Hi Chris, I've already submitted a patch for riscv32 here [1]. [1] https://lists.rtems.org/pipermail/devel/2017-May/017951.html. Cheers, Hesham On Mon, Jun 26, 2017 at 9:57 AM, Chris Johns wrote: > Hello, > > I would like to add aarch64, x86_64, and risc-v to 4.12/rtems-all so these > tools >

RSB Architecture request: aarch64, x86_64, risc-v

2017-06-25 Thread Chris Johns
Hello, I would like to add aarch64, x86_64, and risc-v to 4.12/rtems-all so these tools are always built when regression testing tool set changes. This change makes sure the tools are in a suitable state for those looking to add support for these architectures. To add RISC-V I need the architectu

Re: RISC-V BSP: a clock driver

2017-06-25 Thread Hesham Almatary
On Sun, Jun 25, 2017 at 9:13 PM, Denis Obrezkov wrote: > 2017-06-25 13:04 GMT+02:00 Hesham Almatary : >> >> Hi Denis, >> >> Good to know you're making progress this far. There's no clock driver for >> Spike BSP (the one my port is based on), it just used simulated tick. You'll >> have to implement

Re: RISC-V/HiFive memory limitations

2017-06-25 Thread Joel Sherrill
That doesn't appear to do much more than clear the bss. So no hints on more to do there. The atexit() call and init/fini are handled by RTEMS in portable code. On Jun 25, 2017 6:24 AM, "Denis Obrezkov" wrote: > 2017-06-25 2:50 GMT+02:00 Denis Obrezkov : > >> 2017-06-25 2:15 GMT+02:00 Joel Sherri

Re: RISC-V/HiFive memory limitations

2017-06-25 Thread Denis Obrezkov
2017-06-25 2:50 GMT+02:00 Denis Obrezkov : > 2017-06-25 2:15 GMT+02:00 Joel Sherrill : > >> They are supposed to use the installed linkcmds. >> >> On Jun 24, 2017 6:04 PM, "Denis Obrezkov" >> wrote: >> >>> 2017-06-23 21:03 GMT+02:00 Denis Obrezkov : >>> 2017-06-23 20:16 GMT+02:00 Denis Obrez

Re: RISC-V BSP: a clock driver

2017-06-25 Thread Denis Obrezkov
2017-06-25 13:04 GMT+02:00 Hesham Almatary : > Hi Denis, > > Good to know you're making progress this far. There's no clock driver for > Spike BSP (the one my port is based on), it just used simulated tick. > You'll have to implement both console and click driver for your board. I'd > suggest you

Re: RISC-V BSP: a clock driver

2017-06-25 Thread Hesham Almatary
Hi Denis, Good to know you're making progress this far. There's no clock driver for Spike BSP (the one my port is based on), it just used simulated tick. You'll have to implement both console and click driver for your board. I'd suggest you start with the console driver. Cheers, Hesham On Sun, 2

RISC-V BSP: a clock driver

2017-06-25 Thread Denis Obrezkov
Hello all, I was able to proceed till the rtems_io_initialize function, so it seems to me that now I need to initialize a clock driver. I tried to find the current implementation of the driver in RISC-V BSP, but wasn't able to do it. Hesham, could you clarify the current state of the clock driver