Re: Libbsd situation.

Hello Karel, On 17.07.23 13:12, Karel Gardas wrote:   Hello, if I'm right than RTEMS 6 should be accompanied with libbsd from 6-freebsd-12 branch which should be based on freebsd-12 (stable/12 branch). Please correct me if I'm wrong here. If I'm right above, then there are few things whic

Re: libbsd development policy clarification needed?

On 06.02.23 20:47, Gedare Bloom wrote: On Mon, Feb 6, 2023 at 8:49 AM Sebastian Huber wrote: On 06.02.23 16:06, Gedare Bloom wrote: Yes, thanks. This looks like a good analysis. I would definitely prefer to get master and 6-freebsd-12 into harmony. Then it is a little simpler to discuss the o

Re: libbsd development policy clarification needed?

On Mon, Feb 6, 2023 at 8:49 AM Sebastian Huber wrote: > > On 06.02.23 16:06, Gedare Bloom wrote: > > Yes, thanks. This looks like a good analysis. I would definitely > > prefer to get master and 6-freebsd-12 into harmony. Then it is a > > little simpler to discuss the other problems in libbsd. > >

Re: libbsd development policy clarification needed?

On 06.02.23 16:06, Gedare Bloom wrote: Yes, thanks. This looks like a good analysis. I would definitely prefer to get master and 6-freebsd-12 into harmony. Then it is a little simpler to discuss the other problems in libbsd. Vijay had similar kind of success (and problems) as you did with cherry

Re: libbsd development policy clarification needed?

On 2023-02-06 16:06, Gedare Bloom wrote: On Mon, Feb 6, 2023 at 2:26 AM Christian MAUDERER wrote: On 2023-02-06 10:02, Christian MAUDERER wrote: On 2023-02-05 11:38, Christian Mauderer wrote: Am 04.02.23 um 01:25 schrieb Gedare Bloom: On Fri, Feb 3, 2023 at 3:29 PM Christian Mauderer w

Re: libbsd development policy clarification needed?

On Mon, Feb 6, 2023 at 2:26 AM Christian MAUDERER wrote: > > On 2023-02-06 10:02, Christian MAUDERER wrote: > > On 2023-02-05 11:38, Christian Mauderer wrote: > >> > >> > >> Am 04.02.23 um 01:25 schrieb Gedare Bloom: > >>> On Fri, Feb 3, 2023 at 3:29 PM Christian Mauderer > >>> wrote: > > >>

Re: libbsd development policy clarification needed?

On 2023-02-06 10:02, Christian MAUDERER wrote: On 2023-02-05 11:38, Christian Mauderer wrote: Am 04.02.23 um 01:25 schrieb Gedare Bloom: On Fri, Feb 3, 2023 at 3:29 PM Christian Mauderer wrote: Am 3. Februar 2023 22:52:48 MEZ schrieb Gedare Bloom : On Fri, Feb 3, 2023 at 2:39 PM Christi

Re: libbsd development policy clarification needed?

On 2023-02-05 11:38, Christian Mauderer wrote: Am 04.02.23 um 01:25 schrieb Gedare Bloom: On Fri, Feb 3, 2023 at 3:29 PM Christian Mauderer wrote: Am 3. Februar 2023 22:52:48 MEZ schrieb Gedare Bloom : On Fri, Feb 3, 2023 at 2:39 PM Christian Mauderer wrote: Am 3. Februar 2023 22:12

Re: libbsd development policy clarification needed?

Am 04.02.23 um 01:25 schrieb Gedare Bloom: On Fri, Feb 3, 2023 at 3:29 PM Christian Mauderer wrote: Am 3. Februar 2023 22:52:48 MEZ schrieb Gedare Bloom : On Fri, Feb 3, 2023 at 2:39 PM Christian Mauderer wrote: Am 3. Februar 2023 22:12:06 MEZ schrieb Gedare Bloom : On Fri, Feb 3, 2

Re: libbsd development policy clarification needed?

Hello Christian, On 2/3/23 07:24, Christian MAUDERER wrote: If you want to know some more about the problematic points, I recommend reading this (long) thread: https://lists.rtems.org/pipermail/devel/2023-January/074164.html oh, I've seen that and ignored so far not knowing this will bite

Re: libbsd development policy clarification needed?

On Fri, Feb 3, 2023 at 3:29 PM Christian Mauderer wrote: > > > > Am 3. Februar 2023 22:52:48 MEZ schrieb Gedare Bloom : > >On Fri, Feb 3, 2023 at 2:39 PM Christian Mauderer wrote: > >> > >> > >> > >> Am 3. Februar 2023 22:12:06 MEZ schrieb Gedare Bloom : > >> >On Fri, Feb 3, 2023 at 12:52 PM wro

Re: libbsd development policy clarification needed?

Am 3. Februar 2023 22:52:48 MEZ schrieb Gedare Bloom : >On Fri, Feb 3, 2023 at 2:39 PM Christian Mauderer wrote: >> >> >> >> Am 3. Februar 2023 22:12:06 MEZ schrieb Gedare Bloom : >> >On Fri, Feb 3, 2023 at 12:52 PM wrote: >> >> >> >> Hello Gedare, >> >> >> >> Am 03.02.23 um 19:51 schrieb Gedar

Re: libbsd development policy clarification needed?

On Fri, Feb 3, 2023 at 2:39 PM Christian Mauderer wrote: > > > > Am 3. Februar 2023 22:12:06 MEZ schrieb Gedare Bloom : > >On Fri, Feb 3, 2023 at 12:52 PM wrote: > >> > >> Hello Gedare, > >> > >> Am 03.02.23 um 19:51 schrieb Gedare Bloom: > >> > On Thu, Feb 2, 2023 at 11:24 PM Christian MAUDERER

Re: libbsd development policy clarification needed?

Am 3. Februar 2023 22:12:06 MEZ schrieb Gedare Bloom : >On Fri, Feb 3, 2023 at 12:52 PM wrote: >> >> Hello Gedare, >> >> Am 03.02.23 um 19:51 schrieb Gedare Bloom: >> > On Thu, Feb 2, 2023 at 11:24 PM Christian MAUDERER >> > wrote: >> >> >> >> Hello Karel, >> >> >> >> On 2023-02-02 12:43, Karel

Re: libbsd development policy clarification needed?

On Fri, Feb 3, 2023 at 12:52 PM wrote: > > Hello Gedare, > > Am 03.02.23 um 19:51 schrieb Gedare Bloom: > > On Thu, Feb 2, 2023 at 11:24 PM Christian MAUDERER > > wrote: > >> > >> Hello Karel, > >> > >> On 2023-02-02 12:43, Karel Gardas wrote: > >>> > >>> Guys, > >>> > >>> recently I needed t

Re: libbsd development policy clarification needed?

Hello Gedare, Am 03.02.23 um 19:51 schrieb Gedare Bloom: On Thu, Feb 2, 2023 at 11:24 PM Christian MAUDERER wrote: Hello Karel, On 2023-02-02 12:43, Karel Gardas wrote: Guys, recently I needed to work with RTEMS/NFS. As this is provided by libbsd I took this and following two sentence

Re: libbsd development policy clarification needed?

On Thu, Feb 2, 2023 at 11:24 PM Christian MAUDERER wrote: > > Hello Karel, > > On 2023-02-02 12:43, Karel Gardas wrote: > > > >Guys, > > > > recently I needed to work with RTEMS/NFS. As this is provided by libbsd > > I took this and following two sentences below from master branch > > descript

Re: libbsd development policy clarification needed?

Hello Karel, On 2023-02-02 12:43, Karel Gardas wrote:   Guys, recently I needed to work with RTEMS/NFS. As this is provided by libbsd I took this and following two sentences below from master branch description provided in README I took as granted that master does have all the features whi

Re: [libbsd 00/22] Remove FreeBSD file descriptors and avoid VFS

On 21/10/2022 16:16, Sebastian Huber wrote: On 21/10/2022 16:07, Joel Sherrill wrote: On Thu, Oct 20, 2022 at 7:30 PM Chris Johns > wrote:     On 20/10/2022 7:01 pm, Sebastian Huber wrote: > On 29/08/2022 10:27, Sebastian Huber wrote: >> Hello Chris, >>  

Re: [libbsd 00/22] Remove FreeBSD file descriptors and avoid VFS

On 21/10/2022 16:07, Joel Sherrill wrote: On Thu, Oct 20, 2022 at 7:30 PM Chris Johns > wrote: On 20/10/2022 7:01 pm, Sebastian Huber wrote: > On 29/08/2022 10:27, Sebastian Huber wrote: >> Hello Chris, >> >> On 25/07/2022 08:12, Sebastian Huber w

Re: [libbsd 00/22] Remove FreeBSD file descriptors and avoid VFS

On Thu, Oct 20, 2022 at 7:30 PM Chris Johns wrote: > On 20/10/2022 7:01 pm, Sebastian Huber wrote: > > On 29/08/2022 10:27, Sebastian Huber wrote: > >> Hello Chris, > >> > >> On 25/07/2022 08:12, Sebastian Huber wrote: > >>> On 11/07/2022 15:04, Sebastian Huber wrote: > On 24/06/2022 08:33,

Re: [libbsd 00/22] Remove FreeBSD file descriptors and avoid VFS

On 21/10/2022 02:30, Chris Johns wrote: On 20/10/2022 7:01 pm, Sebastian Huber wrote: On 29/08/2022 10:27, Sebastian Huber wrote: Hello Chris, On 25/07/2022 08:12, Sebastian Huber wrote: On 11/07/2022 15:04, Sebastian Huber wrote: On 24/06/2022 08:33, Sebastian Huber wrote: This patch set r

Re: [libbsd 00/22] Remove FreeBSD file descriptors and avoid VFS

On 20/10/2022 7:01 pm, Sebastian Huber wrote: > On 29/08/2022 10:27, Sebastian Huber wrote: >> Hello Chris, >> >> On 25/07/2022 08:12, Sebastian Huber wrote: >>> On 11/07/2022 15:04, Sebastian Huber wrote: On 24/06/2022 08:33, Sebastian Huber wrote: > This patch set removes the FreeBSD fil

Re: [libbsd 00/22] Remove FreeBSD file descriptors and avoid VFS

On 29/08/2022 10:27, Sebastian Huber wrote: Hello Chris, On 25/07/2022 08:12, Sebastian Huber wrote: On 11/07/2022 15:04, Sebastian Huber wrote: On 24/06/2022 08:33, Sebastian Huber wrote: This patch set removes the FreeBSD file descriptors.  The VFS is no longer used if only the USB, SD/MMC

Re: libbsd fails to link on i386

missing to even build it for x86_64 without any drivers. --joel > > > Best regards, > > > > Jan > > > > > > *From:* devel *On Behalf Of *jan.som...@dlr.de > *Sent:* Thursday, August 18, 2022 8:09 PM > *To:* j...@rtems.org; devel@rtems.org >

RE: libbsd fails to link on i386

From: devel On Behalf Of jan.som...@dlr.de Sent: Thursday, August 18, 2022 8:09 PM To: j...@rtems.org; devel@rtems.org Subject: RE: libbsd fails to link on i386 Hi Joel, I remember I spent some time fiddling with the bus.h include order. I can try to have a look at it some time next week

Re: [libbsd 00/22] Remove FreeBSD file descriptors and avoid VFS

Hello Chris, On 25/07/2022 08:12, Sebastian Huber wrote: On 11/07/2022 15:04, Sebastian Huber wrote: On 24/06/2022 08:33, Sebastian Huber wrote: This patch set removes the FreeBSD file descriptors.  The VFS is no longer used if only the USB, SD/MMC, network, PCI, and NVMe support is used by t

Re: libbsd fails to link on i386

On Thu, Aug 18, 2022, 1:09 PM wrote: > Hi Joel, > > > > I remember I spent some time fiddling with the bus.h include order. > > I can try to have a look at it some time next week. > Thanks. > > Best regards, > > > > Jan > > > > *From:* devel *On Behalf Of *Joel Sherrill > *Sent:* Wednesd

RE: libbsd fails to link on i386

Hi Joel, I remember I spent some time fiddling with the bus.h include order. I can try to have a look at it some time next week. Best regards, Jan From: devel On Behalf Of Joel Sherrill Sent: Wednesday, August 17, 2022 11:24 PM To: rtems-de...@rtems.org Subject: libbsd fails to l

Re: libbsd fails to link on i386

On Wed, Aug 17, 2022 at 6:47 PM Chris Johns wrote: > On 18/8/2022 7:23 am, Joel Sherrill wrote: > > I think the wrong bus.h must be being included somewhere. These are > static > > inline methods on the i386. Hopefully a simple patch for someone who > knows what > > to do: > > Could it be install

Re: libbsd fails to link on i386

On 18/8/2022 7:23 am, Joel Sherrill wrote: > I think the wrong bus.h must be being included somewhere. These are static > inline methods on the i386. Hopefully a simple patch for someone who knows > what > to do: Could it be installed with the BSP? Does it happen with a clean prefix? Chris _

Re: [libbsd 00/22] Remove FreeBSD file descriptors and avoid VFS

On 11/07/2022 15:04, Sebastian Huber wrote: On 24/06/2022 08:33, Sebastian Huber wrote: This patch set removes the FreeBSD file descriptors.  The VFS is no longer used if only the USB, SD/MMC, network, PCI, and NVMe support is used by the application.  This change significantly reduce the memor

Re: libbsd tests not linking

On Sun, Jul 24, 2022, 7:55 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 24/07/2022 00:31, Joel Sherrill wrote: > > Binary file > > > build/arm-rtems6-xilinx_zynq_a9_qemu-default/freebsd/lib/libc/stdio/fgetln.c.12.o > > > matches > > Binary file build/arm-rtems6-xilinx_zynq_

Re: libbsd tests not linking

On 24/07/2022 00:31, Joel Sherrill wrote: Binary file build/arm-rtems6-xilinx_zynq_a9_qemu-default/freebsd/lib/libc/stdio/fgetln.c.12.o matches Binary file build/arm-rtems6-xilinx_zynq_a9_qemu-default/libbsd.a matches b.log:/home/joel/rtems-work/rtems-libbsd/build/arm-rtems6-xilinx_zynq_a9_qemu

Re: [libbsd 00/22] Remove FreeBSD file descriptors and avoid VFS

On 24/06/2022 08:33, Sebastian Huber wrote: This patch set removes the FreeBSD file descriptors. The VFS is no longer used if only the USB, SD/MMC, network, PCI, and NVMe support is used by the application. This change significantly reduce the memory usage of LibBSD for these applications. Usi

Re: [libbsd 1/7] CONTRIBUTING.rst: Add FreeBSD baseline update hints

On 7/7/22 14:02, Sebastian Huber wrote: +Performa the following steps to do a FreeBSD baseline update: Small typo here. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [libbsd 10/22] Update CONTRIBUTING.rst

On 27/06/2022 06:40, Chris Johns wrote: Hi Sebastian, Thank you for this submission. It will take a time for me to work through all the changes in detail and I may need your assistance if that is OK? I am heading out of town so I am sorry it will not be this week. On 24/6/2022 4:33 pm, Sebastia

Re: [libbsd 10/22] Update CONTRIBUTING.rst

On 27/6/2022 2:40 pm, Chris Johns wrote: > We was this micro-optimisations. We saw this as micro-optimisations. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [libbsd 10/22] Update CONTRIBUTING.rst

Hi Sebastian, Thank you for this submission. It will take a time for me to work through all the changes in detail and I may need your assistance if that is OK? I am heading out of town so I am sorry it will not be this week. On 24/6/2022 4:33 pm, Sebastian Huber wrote: > +Porting Advice > +==

Re: [libbsd 0/4] Replace LPC Ethernet interface driver

OK Chris On 23/6/2022 7:20 pm, Sebastian Huber wrote: > The standard FreeBSD MII support causes severe problems on the LPC3200 > chip family. If an Ethernet module register is accessed while there is > no clock from the PHY, the chip completely locks up and only an external > watchdog can recove

Re: [libbsd 00/22] Move content of libbsd.txt

On 24/5/2022 12:33 am, Sebastian Huber wrote: > This patch set updates the README.md and CONTRIBUTING.md files with > content from libbsd.txt. The format is converted to reST which is also > supported by Github and fits to rtems-docs. > > For the final results see: > > https://github.com/sebhub/

Re: libbsd zynqmp cpu freq for slcr calc

On 15/10/21 5:33 am, Kinsey Moore wrote: > On 10/14/2021 10:18, Joel Sherrill wrote: >> On Thu, Oct 14, 2021 at 9:56 AM Kinsey Moore >> wrote: >>> On 10/14/2021 01:40, Chris Johns wrote: Hi, I have come across this define in zynqmp_slcr.h: #define ZYNQMP_DEFAULT_PS_CLK_FR

Re: libbsd zynqmp cpu freq for slcr calc

On 10/14/2021 10:18, Joel Sherrill wrote: On Thu, Oct 14, 2021 at 9:56 AM Kinsey Moore wrote: On 10/14/2021 01:40, Chris Johns wrote: Hi, I have come across this define in zynqmp_slcr.h: #define ZYNQMP_DEFAULT_PS_CLK_FREQUENCY What if the cpu freq is changed by a user? If this valu

Re: libbsd zynqmp cpu freq for slcr calc

On Thu, Oct 14, 2021 at 9:56 AM Kinsey Moore wrote: > > On 10/14/2021 01:40, Chris Johns wrote: > > Hi, > > > > I have come across this define in zynqmp_slcr.h: > > > > #define ZYNQMP_DEFAULT_PS_CLK_FREQUENCY > > > > What if the cpu freq is changed by a user? If this value still valid? >

Re: libbsd zynqmp cpu freq for slcr calc

On 10/14/2021 01:40, Chris Johns wrote: Hi, I have come across this define in zynqmp_slcr.h: #define ZYNQMP_DEFAULT_PS_CLK_FREQUENCY What if the cpu freq is changed by a user? If this value still valid? If CPU frequency scaling is used, I believe this value remains unchanged. This is

Re: libbsd: Conditional compilation of tests

On 10/5/2021 02:48, Chris Johns wrote: On 5/10/21 10:27 am, Kinsey Moore wrote: Currently debugger01 is the only user of the test-if-library in libbsd and it doesn't seem to work as expected. The configure step that detects libdebugger occurs and succeeds as it should for the zynq a9 qemu BSP,

Re: libbsd: Conditional compilation of tests

On 5/10/21 10:27 am, Kinsey Moore wrote: > Currently debugger01 is the only user of the test-if-library in libbsd and it > doesn't seem to work as expected. The configure step that detects libdebugger > occurs and succeeds as it should for the zynq a9 qemu BSP, but debugger01.exe > never gets compi

Re: libbsd kernel namespace generation

On Fri, Jul 23, 2021, 2:00 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello Chris, > > On 22/07/2021 10:44, Chris Johns wrote: > > Hello, > > > > Libbsd uses the pre-processor to map all the kernel calls into a libbsd > kernel > > name space by prepending _bsd_ to each symbo

Re: libbsd kernel namespace generation

On 23/7/21 5:00 pm, Sebastian Huber wrote: > Hello Chris, > > On 22/07/2021 10:44, Chris Johns wrote: >> Hello, >> >> Libbsd uses the pre-processor to map all the kernel calls into a libbsd >> kernel >> name space by prepending _bsd_ to each symbol. The script ... >> >> https://git.rtems.org/rtem

Re: libbsd kernel namespace generation

Hello Chris, On 22/07/2021 10:44, Chris Johns wrote: Hello, Libbsd uses the pre-processor to map all the kernel calls into a libbsd kernel name space by prepending _bsd_ to each symbol. The script ... https://git.rtems.org/rtems-libbsd/tree/create-kernel-namespace.sh?h=6-freebsd-12 ... genera

Re: [libbsd] README: Mention SMP requirements

Thanks. On Tue, Jun 15, 2021 at 10:45 AM Sebastian Huber wrote: > > --- > README.md | 7 +++ > 1 file changed, 7 insertions(+) > > diff --git a/README.md b/README.md > index 19c9023e..0438653d 100644 > --- a/README.md > +++ b/README.md > @@ -293,3 +293,10 @@ Escape character is '^]'. > RTEM

Re: [libbsd] EPOCH(9): Fix epoch call and drain

On Tue, Jun 15, 2021 at 9:12 AM Sebastian Huber wrote: > > On 15/06/2021 17:10, Gedare Bloom wrote: > > Does this add a constraint in libbsd that it only works with SMP for > > schedulers that support thread pinning? Is that a problem at all? Last > > I checked, not all the SMP schedulers have pin

Re: [libbsd] EPOCH(9): Fix epoch call and drain

On 15/06/2021 17:10, Gedare Bloom wrote: Does this add a constraint in libbsd that it only works with SMP for schedulers that support thread pinning? Is that a problem at all? Last I checked, not all the SMP schedulers have pinning. Actually, I think only the EDF SMP scheduler supports pinning.

Re: [libbsd] EPOCH(9): Fix epoch call and drain

Does this add a constraint in libbsd that it only works with SMP for schedulers that support thread pinning? Is that a problem at all? Last I checked, not all the SMP schedulers have pinning. Actually, I think only the EDF SMP scheduler supports pinning. On Fri, Jun 11, 2021 at 12:46 AM Sebastian

Re: [libbsd] How to install machine header files?

On 08/04/2021 13:35, jan.som...@dlr.de wrote: @Sebastian: Do you have a suggestion how I could resolve this? I think you have the most experience with the libbsd build system. Sorry, I don't have an off hand solution for this. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 P

RE: [libbsd] How to install machine header files?

..@rtems.org; devel@rtems.org > Subject: RE: [libbsd] How to install machine header files? > > > -Original Message- > > From: Chris Johns > > Sent: Thursday, April 1, 2021 6:25 AM > > To: Sommer, Jan ; devel@rtems.org > > Subject: Re: [libbsd] How to install

Re: libbsd: Backport fd_set size fixes for racoon and ping6 to 5

On 29/03/2021 16:57, Gedare Bloom wrote: On Mon, Mar 29, 2021 at 8:47 AM Christian MAUDERER wrote: Hello Gedare, Am 29.03.21 um 16:40 schrieb Gedare Bloom: On Mon, Mar 29, 2021 at 1:31 AM Christian MAUDERER wrote: Hello Gedare, Am 26.03.21 um 16:03 schrieb Gedare Bloom: seems fine to m

RE: [libbsd] How to install machine header files?

> -Original Message- > From: Chris Johns > Sent: Thursday, April 1, 2021 6:25 AM > To: Sommer, Jan ; devel@rtems.org > Subject: Re: [libbsd] How to install machine header files? > > On 1/4/21 6:37 am, jan.som...@dlr.de wrote: > > Hello, > > > > I s

Re: [libbsd] How to install machine header files?

On 1/4/21 6:37 am, jan.som...@dlr.de wrote: > Hello, > > I stumbled upon some include path problems in libbsd while looking at Chris' > ptpd port and I am not sure what is the recommended way to solve it. > It starts with "freebsd/sys/sys/bus.h" including "machine/_bus.h". > Currently, this will

Re: libbsd: Backport fd_set size fixes for racoon and ping6 to 5

On Mon, Mar 29, 2021 at 8:47 AM Christian MAUDERER wrote: > > Hello Gedare, > > Am 29.03.21 um 16:40 schrieb Gedare Bloom: > > On Mon, Mar 29, 2021 at 1:31 AM Christian MAUDERER > > wrote: > >> > >> Hello Gedare, > >> > >> Am 26.03.21 um 16:03 schrieb Gedare Bloom: > >>> seems fine to me. > >> >

Re: libbsd: Backport fd_set size fixes for racoon and ping6 to 5

Hello Gedare, Am 29.03.21 um 16:40 schrieb Gedare Bloom: On Mon, Mar 29, 2021 at 1:31 AM Christian MAUDERER wrote: Hello Gedare, Am 26.03.21 um 16:03 schrieb Gedare Bloom: seems fine to me. Thanks. I just wanted to push the patches and noted that there haven't been any changes to the 5 b

Re: libbsd: Backport fd_set size fixes for racoon and ping6 to 5

On Mon, Mar 29, 2021 at 1:31 AM Christian MAUDERER wrote: > > Hello Gedare, > > Am 26.03.21 um 16:03 schrieb Gedare Bloom: > > seems fine to me. > > Thanks. > > I just wanted to push the patches and noted that there haven't been any > changes to the 5 branch of libbsd since the release. But there

Re: libbsd: Backport fd_set size fixes for racoon and ping6 to 5

Hello Gedare, Am 26.03.21 um 16:03 schrieb Gedare Bloom: seems fine to me. Thanks. I just wanted to push the patches and noted that there haven't been any changes to the 5 branch of libbsd since the release. But there have been some fixes on the 5-freebsd-12 branch. Did I miss something and

Re: libbsd: Backport fd_set size fixes for racoon and ping6 to 5

seems fine to me. On Fri, Mar 26, 2021 at 7:14 AM Christian MAUDERER wrote: > > Hello, > > I would like to backport the following patches to 5 and 5-freebsd-12: > > https://git.rtems.org/rtems-libbsd/commit/?h=6-freebsd-12&id=e7fb073f3a1040847daab3ef917aeade755eb30b > https://git.rtems.org/rtems-

Re: LibBSD PowerPC motorola_shared BSP PCI Support

On Wed, Nov 4, 2020 at 6:28 AM Heinz Junkes wrote: > Hello, Chris, > unfortunately it is not quite so simple. The Beatnik board uses > for the Ethernet the Marvell Discovery II MV64360 (GT64360) > and there two of the three built-in Ethernet controllers. > > Till Straumann has written a driver fo

Re: LibBSD PowerPC motorola_shared BSP PCI Support

Hello, Chris, unfortunately it is not quite so simple. The Beatnik board uses for the Ethernet the Marvell Discovery II MV64360 (GT64360) and there two of the three built-in Ethernet controllers. Till Straumann has written a driver for it called "mve" and unfortunately it is not available in fr

Re: LibBSD PowerPC motorola_shared BSP PCI Support

Hello, Joel, You are right, for the MVME6100 the configuration in libbsd is still missing. There is also missing the old NIC. Chris has already sent me information about it. I'll try to do that next week. But I have to put two MVME6100s into production by the end of the month. If I can't do tha

Re: LibBSD PowerPC motorola_shared BSP PCI Support

On Thu, Oct 29, 2020, 6:07 AM Heinz Junkes wrote: > I can now run the test programs of libbsd. But on the MVME6100 > no network interfaces gets found. > > MVME6100> netShut > /- > config addr is 0xf1000cf8 > config data is 0xf1000cfc > Welcome to RTEMS rtem

Re: LibBSD PowerPC motorola_shared BSP PCI Support

On Thu, Oct 29, 2020, 7:44 AM Heinz Junkes wrote: > I have now changed to a more modern board: MVME2500 > And built rtems6 and libbsd for qoriq_e500. > Since you mention it worked in the spring, does it work with rtems5? > > Unfortunately the board hangs when loading the image: > > MVME2500=>

Re: LibBSD PowerPC motorola_shared BSP PCI Support

On 29/10/20 11:44 pm, Heinz Junkes wrote: > I have now changed to a more modern board: MVME2500 > And built rtems6 and libbsd for qoriq_e500. Thank you for testing and reporting. > Unfortunately the board hangs when loading the image: > > MVME2500=> setenv tfile dhcpcd02_6 > MVME2500=> run rtems

Re: LibBSD PowerPC motorola_shared BSP PCI Support

I have now changed to a more modern board: MVME2500 And built rtems6 and libbsd for qoriq_e500. Unfortunately the board hangs when loading the image: MVME2500=> setenv tfile dhcpcd02_6 MVME2500=> run rtems_myTests reading mvme2500.dtb 12363 bytes read in 32 ms (377 KiB/s) Speed: 1000, full duple

Re: LibBSD PowerPC motorola_shared BSP PCI Support

I can now run the test programs of libbsd. But on the MVME6100 no network interfaces gets found. MVME6100> netShut /- config addr is 0xf1000cf8 config data is 0xf1000cfc Welcome to RTEMS rtems-6.0.0 (PowerPC/Generic (classic FPU)/beatnik) CPU: MPC7457 Board

Re: LibBSD PowerPC motorola_shared BSP PCI Support

Thanks, I got further and the first start doesn't look that bad ;-) Welcome to RTEMS rtems-6.0.0 (PowerPC/Generic (classic FPU)/beatnik) CPU: MPC7457 Board Type: MVME6100-0163 (S/N E173D27) Bus Clock Freq: 1 Hz CPU Clock Freq: 126654 Hz Memory: 536870912 bytes ---

Re: LibBSD PowerPC motorola_shared BSP PCI Support

I On Tue, Oct 27, 2020, 12:42 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > On 27/10/2020 15:41, Joel Sherrill wrote: > > > > > > On Tue, Oct 27, 2020 at 9:23 AM Heinz Junkes > > wrote: > > > > I am currently trying git rtems6. > > > >

Re: LibBSD PowerPC motorola_shared BSP PCI Support

On 27/10/2020 15:41, Joel Sherrill wrote: On Tue, Oct 27, 2020 at 9:23 AM Heinz Junkes > wrote: I am currently trying git rtems6. ../source-builder/sb-set-builder --prefix=$HOME/.rtems --log powerpc_beatnik.log --no-clean --target=powerpc-rtems6

Re: LibBSD PowerPC motorola_shared BSP PCI Support

On Tue, Oct 27, 2020 at 9:23 AM Heinz Junkes wrote: > I am currently trying git rtems6. > > ../source-builder/sb-set-builder --prefix=$HOME/.rtems --log > powerpc_beatnik.log --no-clean --target=powerpc-rtems6 > --with-rtems-bsp=beatnik 6/rtems-powerpc 6/rtems-kernel > > works … > > Unfortunately

Re: LibBSD PowerPC motorola_shared BSP PCI Support

I am currently trying git rtems6. ../source-builder/sb-set-builder --prefix=$HOME/.rtems --log powerpc_beatnik.log --no-clean --target=powerpc-rtems6 --with-rtems-bsp=beatnik 6/rtems-powerpc 6/rtems-kernel works … Unfortunately It fails here: ../source-builder/sb-set-builder --prefix=$HOME/.

Re: LibBSD PowerPC motorola_shared BSP PCI Support

On 26/10/20 7:32 pm, Heinz Junkes wrote: > Good morning Chris, > i will now try out libbsd on a MVME6100 (beatnik). > Is the mentioned patch in git? The PCI patch is in rtems-libbsd.git on the master and 6-freebsd-12 branches. > Or do I have to prepare something special? Yes I think you may nee

Re: LibBSD PowerPC motorola_shared BSP PCI Support

Good morning Chris, i will now try out libbsd on a MVME6100 (beatnik). Is the mentioned patch in git? Or do I have to prepare something special? Thanks Heinz > On 21. Oct 2020, at 02:44, Chris Johns wrote: > > On 21/10/20 2:52 am, Sebastian Huber wrote: >> On 20/10/2020 03:52, chr...@rtems.org w

Re: LibBSD PowerPC motorola_shared BSP PCI Support

On 21/10/20 2:52 am, Sebastian Huber wrote: > On 20/10/2020 03:52, chr...@rtems.org wrote: > >> Tested on a MVME2700 (mvme2307) BSP: >> >> nexus0: >> pcib0 pcibus 0 on motherboard >> pci0: on pcib0 >> pci0: at device 0.0 (no driver attached) >> pci0: at device 11.0 (no driver attached) >> pci0

Re: LibBSD PowerPC motorola_shared BSP PCI Support

On 20/10/2020 03:52, chr...@rtems.org wrote: Tested on a MVME2700 (mvme2307) BSP: nexus0: pcib0 pcibus 0 on motherboard pci0: on pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 11.0 (no driver attached) pci0: at device 11.1 (no driver attached) pci0: at device 12.0 (no driv

Re: libbsd need --enable-posix any more?

On 13/10/2020 10:06, Chris Johns wrote: LibBSD checks for --enable-posix. Is this check needed with rtems.git master? I haven't tried it out. It would be good to get rid of this requirement. ___ devel mailing list devel@rtems.org http://lists.rtems.or

Re: libbsd master and 6-freebsd-12 branch different

On 29/9/20 2:43 pm, Sebastian Huber wrote: > On 29/09/2020 04:11, Chris Johns wrote: > >> A few recent patches have been pushed to master but not the 6-freebsd-12 >> branch. >> I was wondering if some should be on the 6-freebsd-12 branch as well? > > Some patches are due to FreeBSD API changes.

Re: libbsd master and 6-freebsd-12 branch different

On 29/09/2020 04:11, Chris Johns wrote: A few recent patches have been pushed to master but not the 6-freebsd-12 branch. I was wondering if some should be on the 6-freebsd-12 branch as well? Some patches are due to FreeBSD API changes. I will do a build run to check if the other patches can b

Re: libbsd master is broken with powerpc

On 23/9/20 4:15 pm, Sebastian Huber wrote: > On 23/09/2020 07:11, Chris Johns wrote: > >> Sorry for the noise. I pulled the wrong repo. Update the repo and it builds. > > I worked on the libbsd build in the last days. Yes and it was my mistake I had not updated the right repo. > This is my fina

Re: libbsd master is broken with powerpc

On 23/09/2020 07:11, Chris Johns wrote: Sorry for the noise. I pulled the wrong repo. Update the repo and it builds. I worked on the libbsd build in the last days. This is my final status: https://devel.rtems.org/wiki/Release/6/Waf%20BSP%20Checklist What we need now are test runs with build

Re: libbsd master is broken with powerpc

On 23/9/20 3:08 pm, Chris Johns wrote: > Hi, > > I am seeing this ... > > '-o/opt/work/chris/rtems/libbsd/rtems-libbsd.git/build/powerpc-rtems6-psim-default/linux/drivers/soc/fsl/qbman/qman_ccsr.c.19.o'] > In file included from > ../../rtemsbsd/include/machine/rtems-bsd-kernel-space.h:59, >

Re: libbsd master broken for pc686 BSP

On 9/19/20 12:15 AM, Joel Sherrill wrote: > If you really meant the master, try 6-freebsd12 instead.  > Not sure, but Christian in a thread 'How to use lvgl on pc386 BSP' analysed my report about missing input.h IIRC and concluded that I need to use master, so hence I'm here on master. > Branch

Re: libbsd master broken for pc686 BSP

If you really meant the master, try 6-freebsd12 instead. Branch names are complicated in libbsd because they need to reflect RTEMS and FreeBSD version. I'm not really sure how to make this any less confusing. :( --joel On Fri, Sep 18, 2020 at 3:01 PM Karel Gardas wrote: > > Hello, > > I've ju

Re: libbsd configure removes -D flags from CFLAGS of pkg-config

On Mon, Sep 14, 2020 at 12:15 AM Chris Johns wrote: > On 14/9/20 3:06 pm, Sebastian Huber wrote: > > On 14/09/2020 01:46, Chris Johns wrote: > >> On 13/9/20 3:46 am, Sebastian Huber wrote: > >>> Hello, > >>> > >>> I can't build the libbsd for powerpc/beatnik: > >>> > >>> -

Re: libbsd configure removes -D flags from CFLAGS of pkg-config

On 14/9/20 3:06 pm, Sebastian Huber wrote: > On 14/09/2020 01:46, Chris Johns wrote: >> On 13/9/20 3:46 am, Sebastian Huber wrote: >>> Hello, >>> >>> I can't build the libbsd for powerpc/beatnik: >>> >>> - >>> Compiler version (powerpc-rtems6-gcc) >>> 10.

Re: libbsd configure removes -D flags from CFLAGS of pkg-config

On 14/09/2020 01:46, Chris Johns wrote: On 13/9/20 3:46 am, Sebastian Huber wrote: Hello, I can't build the libbsd for powerpc/beatnik: - Compiler version (powerpc-rtems6-gcc) 10.2.1 20200904 (RTEMS 6, RSB 47f32b8b1a597b5ed3475722bdc155249ef51115, Ne

Re: libbsd configure removes -D flags from CFLAGS of pkg-config

On 13/9/20 3:46 am, Sebastian Huber wrote: > Hello, > > I can't build the libbsd for powerpc/beatnik: > > - > Compiler version (powerpc-rtems6-gcc) > 10.2.1 20200904 (RTEMS 6, RSB 47f32b8b1a597b5ed3475722bdc155249ef51115, Newlib > a0d7982) > Opening and

Re: libbsd rtems 5 branches

On 09/07/2020 09:17, jan.som...@dlr.de wrote: -Original Message- From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Sebastian Huber Sent: Tuesday, July 7, 2020 3:22 PM To:j...@rtems.org;rtems-de...@rtems.org Subject: Re: libbsd rtems 5 branches On 07/07/2020 15:19, Joel

RE: libbsd rtems 5 branches

> -Original Message- > From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Sebastian > Huber > Sent: Tuesday, July 7, 2020 3:22 PM > To: j...@rtems.org; rtems-de...@rtems.org > Subject: Re: libbsd rtems 5 branches > > On 07/07/2020 15:19, Joel Sherrill wrot

Re: libbsd rtems 5 branches

On 07/07/2020 15:19, Joel Sherrill wrote: Hi What's the difference between these two branches?   remotes/origin/5 This branch synchronizes with the FreeBSD master.   remotes/origin/5-freebsd-12 This branch synchronizes with the FreeBSD 12 branch. Both are for RTEMS 5. -- Sebastian Hu

RE: libbsd fails to build on master for i386

Hi Jeff, yes, this is known, but IIRC the libbsd should build, if you turn off the e1000 module in the buildset. We prepared the iflib patchset for the FreeBSD branch first, because of the upcoming release. There is also one in preparation for master, but got delayed since I wanted to finish th

Re: Libbsd Undefined References When Running FACE Conformance Tests

On 30/03/2020 17:18, Joel Sherrill wrote: On Mon, Mar 30, 2020 at 9:42 AM Sebastian Huber > wrote: On 30/03/2020 16:37, Joel Sherrill wrote: > + What's the relationship between the master and 5-freebsd-12? https://github.com/R

Re: Libbsd Undefined References When Running FACE Conformance Tests

On Mon, Mar 30, 2020 at 9:42 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 30/03/2020 16:37, Joel Sherrill wrote: > > > + What's the relationship between the master and 5-freebsd-12? >> https://github.com/RTEMS/rtems-libbsd#branches > > > That doesn't answer whether the mast

Re: Libbsd Undefined References When Running FACE Conformance Tests

On 30/03/2020 16:37, Joel Sherrill wrote: > + What's the relationship between the master and 5-freebsd-12? https://github.com/RTEMS/rtems-libbsd#branches That doesn't answer whether the master simply tracks FreeBSD or whether it includes the RTEMS modifications. Hm, to me it is obviou

  1   2   3   >