How to specify a BSP variant to Configure?

[Claus, Ric]

It sounds like "multiprocessing" is more akin to what I'm used to referring to as "distributed" or "cluster processing".  So maybe stick one of those words in there somewhere?

Thanks, Joel.

  Ric


On Jun 7, 2013, at 4:36 PM, Joel Sherrill wrote:

> Multiprocessing is for what would now be considered more loosely coupled systems. Independent CPUs and memory.. Different executables.. Communicating over shared memory usually.. Classic API calls converted to RPCs transparently.
> 
> SMP is the newer (post 4.10) support for SMP.
> 
> With that, any suggestions for help text changes? :)
> 
> "Claus, Ric" <claus at slac.stanford.edu> wrote:
> 
> 
> Sorry for the noise, but it _does_ work.  I was somehow referencing a source tree that didn't hadn't been updated with the xilinx-zynq BSP, so of course configure didn't find the variants.  Grumble.
> 
> In the process of figuring this out, I saw that configure has the options --enable-multiprocessing and --enable-smp.  What's the difference?  Maybe the configure --help line could be made clearer?
> 
>        Ric
> 
> 
> On Jun 7, 2013, at 9:58 AM, Claus, Ric wrote:
> 
>> Sorry, but
>> 
>> configure [...] --enable-rtemsbsp="xilinx_zynq_a9_qemu" [...]
>> 
>> doesn't select that variant.  However, it did show up in the preceding bootstrap.  So how do I select it?
>> 
>> Ric
>> 
>> ________________________________________
>> From: rtems-devel-bounces at rtems.org [rtems-devel-bounces at rtems.org] On Behalf Of Sebastian Huber [sebastian.huber at embedded-brains.de]
>> Sent: Friday, June 07, 2013 12:02 AM
>> To: rtems-devel at rtems.org
>> Subject: Re: How to specify a BSP variant to Configure?
>> 
>> Hello,
>> 
>> On 06/07/2013 02:03 AM, Claus, Ric wrote:
>>> I should know this, but I'm stuck.  After cloning the rtems repository, I tried various values of enable-rtemsbsp for:
>>> 
>>> ../src/configure --target=arm-rtems4.11 --enable-posix --enable-networking --enable-rdbg --enable-cxx --enable-maintainer-mode --enable-multiprocessing --enable-rtemsbsp="xilinx-zynq" --prefix=$TARGET_DIR
>>> 
>>> e.g., rtemsbsp=xilinx_zynq, xilinx_zynq_a9_qemu, etc., all with no mention of the configured BSP at the end of the configure output.  I don't get it.  I've never been able to make configuration for BSP variants work and don't see how to do it in the Getting Started guide or any other place, so maybe I should ask.
>>> 
>> 
>> the BSP name is determined by the make/custom/*.cfg names, e.g.
>> 
>> xilinx_zynq_a9_qemu
>> xilinx_zynq_a9_qemu_smp
>> 
>>> Anyway, once I get an out-of-the-box configuration to work, could someone please tell me the intended way to reconfigure a BSP for our needs?  Currently xilinx-zynq has two qemu make/custom variants and a value for PERIPHCLK in configure.ac that aren't appropriate to our hardware.  Am I to add new make/custom files?  Do I edit configure.ac and then have git complain every time I try to update to the head, or can such changes be made somehow with the configure command?
>> 
>> You can change BSP options with the configure command line, e.g.
>> 
>> configure [...] BSP_ARM_A9MPCORE_PERIPHCLK=123 [...]
>> 
>> This BSP needs very likely some adjustments to run on real hardware.  Feel free
>> to send patches.
>> 
>>> 
>>> Curiously, xilinx_zynq_a9_qemu.cfg gives -mfloat-abi=hard.  I thought RTEMS didn't support hardware floating point context switching.  Am I mixing things up, or is this valid only for qemu?  For real hardware, should I specify -mfloat-abi=soft?
>> 
>> The ARM port now supports Neon and VFP-D32.  See also
>> 
>> http://www.rtems.org/wiki/index.php/ARM-EABI
>> 
>> --
>> Sebastian Huber, embedded brains GmbH
>> 
>> Address : Dornierstr. 4, D-82178 Puchheim, Germany
>> Phone   : +49 89 189 47 41-16
>> Fax     : +49 89 189 47 41-09
>> E-Mail  : sebastian.huber at embedded-brains.de
>> PGP     : Public key available on request.
>> 
>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>> _______________________________________________
>> rtems-devel mailing list
>> rtems-devel at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-devel
>> 
>> _______________________________________________
>> rtems-devel mailing list
>> rtems-devel at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-devel
> 
> 
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel