Re: [PATCH] user/index: Add myself to the list of copyrights

Thanks. I just pushed it. On 13/08/2019 10:15, Vijay Kumar Banerjee wrote: > --- > user/index.rst | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/user/index.rst b/user/index.rst > index eff85f3..0e644c9 100644 > --- a/user/index.rst > +++ b/user/index.rst > @@ -10,6 +10,7 @@ RTEMS User

Re: [PATCH v2] rtems-record: New program

- Am 15. Aug 2019 um 8:26 schrieb Chris Johns chr...@rtems.org: > On 15/8/19 4:05 pm, Sebastian Huber wrote: >> - Am 15. Aug 2019 um 2:09 schrieb Chris Johns chr...@rtems.org: >> >>> On 14/8/19 3:19 pm, Sebastian Huber wrote: On 14/08/2019 03:57, Chris Johns wrote: > On 13/8/19 3

Re: GSoC Final report review

On 14/08/2019 18:41, Vijay Kumar Banerjee wrote: > Hello all, > > I have prepared a draft for the GSoC final report. It would be nice to have > some review on it before I push it to the blog. The google docs link [1] > contains a paste from the .md file that will be converted to html for the > blo

Re: [PATCH v2] rtems-record: New program

On 15/8/19 5:33 pm, Sebastian Huber wrote:> > I don't think it is worth to add this switch. OK. > I will work on this program in August and September. > Thank you. I have no other specific issues with the code. Chris ___ devel mailing list devel@rt

Re: LibBSD master vs 5-freebsd12 TI frame buffer patches

On 15/8/19 10:36 am, Chris Johns wrote: > Currently the RSB libbsd package is building and installing LibBSD `master` > and > I was looking to move this to `5-freebsd12` to align it with the needs of a > release. The curl package does not build with 5-freebsd12. It fails a simple link test durin

GSoC 2019 : POSIX Complaince - Fenv methods not returning expected outputs.

Hello, In yesterday's weekly meeting I mentioned about fenv problems I faced while developing testsuite. . Here is a very raw patch of my code as testsuite is still in development. . == Error 1 == I took

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

On Wed, Aug 14, 2019 at 8:56 PM Hesham Almatary wrote: > On Wed, 14 Aug 2019 at 16:18, Vaibhav Gupta > wrote: > > > > > > > > On Wed, Aug 14, 2019, 8:09 PM Joel Sherrill wrote: > >> > >> On Wed, Aug 14, 2019 at 9:35 AM Vaibhav Gupta > wrote: > >> > > >> > You are also getting same error :( > >

Re: [PATCH v1] Add steps to test Newlib patch.

Is this a duplicate of the other "patch v1 Add steps to test Newlib patch." or this one replaces it? On Wed, Aug 14, 2019 at 11:45 PM Vaibhav Gupta wrote: > Update the checksum to be used for the Newlib patches. > Earlier it was msd5, but it is depreciated for security > reasons. Now RSB accepts

Re: [PATCH v1] Remove back-slash in 'pacman' command in 'PDF' section under Arch Linux (installation of Sphinx).

Please don't send multiple identical patches to the mailing list. You may reply to a patch to 'ping' it if you want to get it some attention after it sits for a few days. On Wed, Aug 14, 2019 at 11:44 PM Vaibhav Gupta wrote: > > --- > README.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deleti

RTEMS Muilti-I/O lib is missing

Although git://git.rtems.org/multiio.git is clonable, this repository is not listed as an official RTEMS git repo at git.rtems.org. Seems that multiio lib is not a first class citizen from RTEMS development any more. Why? --Wendell ___ devel mailing lis

Re: [PATCH] dtc.bset: update to 1.4.1 to match qemu

FWIW: I had to build dtc by hand recently. It might be worth it to work up an RSB script for host tooling to help users/developers work with DT. On Wed, Aug 14, 2019 at 5:40 PM Joel Sherrill wrote: > > > > On Wed, Aug 14, 2019, 6:02 PM Chris Johns wrote: >> >> On 15/8/19 8:50 am, Joel Sherrill w

Re: RTEMS Muilti-I/O lib is missing

On Thu, Aug 15, 2019, 10:25 AM Wendell Silva wrote: > Although git://git.rtems.org/multiio.git is clonable, this repository is > not listed as an official RTEMS git repo at git.rtems.org. > > Seems that multiio lib is not a first class citizen from RTEMS development > any more. Why > It never wa

Re: fenv on RISC-V

On Wed, Aug 14, 2019 at 12:44 PM Joel Sherrill wrote: > > Hi > > I emailed Jim Wilson of SiFive and got a quick response. Much thanks > to him and this is his reply: > > == > I don't have any embedded hardware that I can use for testing. I just > have linux and simulators (qemu, g

Re: RTEMS Muilti-I/O lib is missing

On Thu, Aug 15, 2019 at 9:33 AM Joel Sherrill wrote: > > > > On Thu, Aug 15, 2019, 10:25 AM Wendell Silva wrote: >> >> Although git://git.rtems.org/multiio.git is clonable, this repository is not >> listed as an official RTEMS git repo at git.rtems.org. >> >> Seems that multiio lib is not a firs

Re: RTEMS Source Builder failed for MX Linux

Hi Chris, Finally RTEMS build run for MX Linux. I will soon release the patch after testing it. Thanks Himanshu ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Beagle: FDT support in BSP as a GSoC project?

On 12/08/2019 08:18, Chris Johns wrote: > On 12/8/19 3:51 pm, Christian Mauderer wrote: >> >> On 12/08/2019 03:33, Chris Johns wrote: >>> On 12/8/19 9:22 am, Joel Sherrill wrote: On Sun, Aug 11, 2019, 5:47 PM Chris Johns >>> > wrote: On 12/8/19

GSoC 2019 : POSIX Compliance - Final Report

Hello, I have made the draft of my project report on google docs. I have mentioned about each and every task completed and which are in progress. . It would be very helpful for me If I can get reviews on this, will also make required changes. . https://docs.google.com/document/d/1I3FsA0whd2AcLKdagU

Re: [PATCH v1] Add steps to test Newlib patch.

On Thu, Aug 15, 2019 at 8:51 PM Gedare Bloom wrote: > Is this a duplicate of the other "patch v1 Add steps to test Newlib > patch." or this one replaces it? > This one replaces it. Actually I replaced all the previous ones with mine. The commands, steps I have written are based on what worked for

Re: [PATCH v1] Remove back-slash in 'pacman' command in 'PDF' section under Arch Linux (installation of Sphinx).

I apologize for this , will follow the given instructions from next time. - Vaibhav On Thu, Aug 15, 2019 at 8:52 PM Gedare Bloom wrote: > Please don't send multiple identical patches to the mailing list. You > may reply to a patch to 'ping' it if you want to get it some attention > after it sit

Re: Beagle: FDT support in BSP as a GSoC project?

All I meant by "not all drivers" and "small" is that we currently do not include code that the application doesn't have a need for. I don't want that to change. If the application doesn't use i2c or the frame buffer, then those drivers shouldn't' be there. I wasn't attempting to create a new requir

Re: [PATCH v1] Remove back-slash in 'pacman' command in 'PDF' section under Arch Linux (installation of Sphinx).

Pushed. Thanks. On Thu, Aug 15, 2019 at 2:34 PM Vaibhav Gupta wrote: > > I apologize for this , will follow the given instructions from next time. > > - Vaibhav > > On Thu, Aug 15, 2019 at 8:52 PM Gedare Bloom wrote: >> >> Please don't send multiple identical patches to the mailing list. You >>

Re: RTEMS Source Builder failed for MX Linux

On 16/8/19 4:48 am, Himanshu Sekhar Nayak wrote: > Hi Chris, > > Finally RTEMS build run for MX Linux. That is great news. Well done. > I will soon release the patch after testing it. A patch to the user manual adding this distro would be nice. Thanks Chris

Re: fenv on RISC-V

On 16/8/19 1:38 am, Gedare Bloom wrote: > On Wed, Aug 14, 2019 at 12:44 PM Joel Sherrill wrote: >> >> Hi >> >> I emailed Jim Wilson of SiFive and got a quick response. Much thanks >> to him and this is his reply: >> >> == >> I don't have any embedded hardware that I can use for tes

Re: [PATCH] dtc.bset: update to 1.4.1 to match qemu

On 16/8/19 1:24 am, Gedare Bloom wrote: > FWIW: I had to build dtc by hand recently. It might be worth it to > work up an RSB script for host tooling to help users/developers work > with DT. There is support ... https://git.rtems.org/rtems-source-builder/tree/bare/config/devel/dtc.bset The versi

Re: fenv on RISC-V

OK. I am going to through an issue out and then paste another email from Jim Wilson. Let's see if we can figure this one out portably. (1) Every architecture now will have an implementation of fenv. It may be a stub, non-functional fenv implementation. If this is the case, many methods return "-EN