Re: [PATCH 4/6] cmdline: Add cmdline support

On 02/08/17 21:07, Andreas Kölbl wrote: Am 02.08.2017 um 15:54 schrieb Sebastian Huber: On 01/08/17 22:14, Andreas Kölbl wrote: At the moment I didn't implement smp functionality. I will implement it directly after implementing SMP. You can use arm_cortex_a9_get_multiprocessor_cpu_id() in

Re: Optimization issue in RISC-V BSP

Looks like it works fine for me. Congratulations! I wonder how feasible it will be if you tried again with sample ticker (instead of low memory one). On Wed, Aug 2, 2017 at 6:54 PM, Denis Obrezkov wrote: >> > + Special registers >> Yes, this might be the issue,

Re: [PATCH 4/6] cmdline: Add cmdline support

On 02/08/2017 23:54, Sebastian Huber wrote: > On 01/08/17 22:14, Andreas Kölbl wrote: >> Am 01.08.2017 um 13:08 schrieb Sebastian Huber: >>> Why can't you use_CPU_SMP_Get_current_processor() instead of >>> bsp_get_boot_cpu(). >>> >>> Why do you have to use the linker command file to allocate

Re: [PATCH 4/6] cmdline: Add cmdline support

Am 02.08.2017 um 15:54 schrieb Sebastian Huber: > On 01/08/17 22:14, Andreas Kölbl wrote: > >> At the moment I didn't implement smp functionality. I will implement it >> directly after implementing SMP. > > You can use arm_cortex_a9_get_multiprocessor_cpu_id() in all > configurations. > >

Re: /dev/urandom issue

- Sichen Zhao schrieb: > > > On 02/08/17 10:46, Sichen Zhao wrote: > > > >> Hi all, > >> > >> When i use wpa_supplicant to configure WPA, there are an error: > >> > >> Could not open /dev/urandom. > >> wlan0: WPA: Failed to get random data for SNonce > > > >

Re: /dev/urandom issue

- Sichen Zhao schrieb: > > > On 02/08/17 10:46, Sichen Zhao wrote: > > > >> Hi all, > >> > >> When i use wpa_supplicant to configure WPA, there are an error: > >> > >> Could not open /dev/urandom. > >> wlan0: WPA: Failed to get random data for SNonce > > > >

Re: /dev/urandom issue

> On 02/08/17 10:46, Sichen Zhao wrote: > >> Hi all, >> >> When i use wpa_supplicant to configure WPA, there are an error: >> >> Could not open /dev/urandom. >> wlan0: WPA: Failed to get random data for SNonce > > /dev/urandom should not be used. Use getentropy() instead. > The getentropy()

Re: BSP receiving messages via uart

samples/capture uses the shell. I don't know if there is a small shell example. On Wed, Aug 2, 2017 at 5:13 AM, Denis Obrezkov wrote: > Hello all, > > I am developing a small size BSP and want to start receiving messages via > uart. > What is the best way to do it? Are

Re: Optimization issue in RISC-V BSP

On Wed, Aug 2, 2017 at 4:54 AM, Denis Obrezkov wrote: >> > + Special registers >> Yes, this might be the issue, specifically if the port is using >> interrupts. For example, mstatus/mcause/mepc might need to be saved >> and/or reset. >> >> What I'm suspicious of is that

Re: [PATCH 4/6] cmdline: Add cmdline support

On 01/08/17 22:14, Andreas Kölbl wrote: At the moment I didn't implement smp functionality. I will implement it directly after implementing SMP. You can use arm_cortex_a9_get_multiprocessor_cpu_id() in all configurations. Please try to use the functions in in your BSP. If missing, then add

Re: /dev/urandom issue

On 02/08/17 10:46, Sichen Zhao wrote: Hi all, When i use wpa_supplicant to configure WPA, there are an error: Could not open /dev/urandom. wlan0: WPA: Failed to get random data for SNonce /dev/urandom should not be used. Use getentropy() instead. It seems we need /dev/urandom to generate

Re: /dev/urandom issue

2017-08-02 10:46 GMT+02:00 Sichen Zhao : > Hi all, > > When i use wpa_supplicant to configure WPA, there are an error: > > Could not open /dev/urandom. > wlan0: WPA: Failed to get random data for SNonce > > It seems we need /dev/urandom to generate the random data. So how

BSP receiving messages via uart

Hello all, I am developing a small size BSP and want to start receiving messages via uart. What is the best way to do it? Are there any tests for message receiving? -- Regards, Denis Obrezkov ___ devel mailing list devel@rtems.org

Re: Optimization issue in RISC-V BSP

> > > + Special registers > Yes, this might be the issue, specifically if the port is using > interrupts. For example, mstatus/mcause/mepc might need to be saved > and/or reset. > > What I'm suspicious of is that the trap_entry code is the problem, > since it didn't have a chance to get

/dev/urandom issue

Hi all, When i use wpa_supplicant to configure WPA, there are an error: Could not open /dev/urandom. wlan0: WPA: Failed to get random data for SNonce It seems we need /dev/urandom to generate the random