From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] Build tests: analogy, blackfin, rtcan and nios2.
Date: Sat, 26 Dec 2009 23:54:13 +0100 [thread overview]
Message-ID: <4B369415.1090200@domain.hid> (raw)
In-Reply-To: <1261852062.19080.288.camel@domain.hid>
Philippe Gerum wrote:
> On Sat, 2009-12-26 at 19:09 +0100, Gilles Chanteperdrix wrote:
>> Alexis Berlemont wrote:
>>> Hi Gilles,
>>>
>>> Gilles Chanteperdrix wrote:
>>>> Alexis Berlemont wrote:
>>>>> Hi Gilles,
>>>>>
>>>>> Gilles Chanteperdrix wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Since I started talking about it, I have run build tests fixing a few
>>>>>> things here and there. The current status is this (still at the same
>>>>>> place: http://sisyphus.hd.free.fr/~gilles/bx):
>>>>>>
>>>>>> * analogy: I have tried to disable some parts of analogy when compiling
>>>>>> on machines without CONFIG_PCI, as compiling parts using PCI on a
>>>>>> machine without PCI support, give various levels of warning and even
>>>>>> errors depending on the architecture. Doing this, I stumbled across this
>>>>>> compilation error:
>>>>>> http://sisyphus.hd.free.fr/~gilles/bx/beagle/2.6.28-arm-none-linux-gnueabi-gcc-4.3.3/log.html#1
>>>>>> this is with CONFIG_NI_MIO, but without CONFIG_NI_MITE.
>>>>>>
>>>>>> So, Alex, could you:
>>>>>> - fix that error, if this combination is supposed to make sense
>>>>> Yes it makes sense. I think the MITE is integrated into all PCI boards
>>>>> but the driver should work with the MITE disabled (one day, we could add
>>>>> the ISA boards).
>>>>>> - fix the Kconfig/Makefile so that no PCI code is compiled if CONFIG_PCI
>>>>>> is not set (I tried and do this myself, but better one who knows than
>>>>>> 100 who have to search...). As I said, doing this result in various
>>>>>> levels of success depending on the architecture.
>>>>> Ack. I will fix these problems as quickly as possible.
>>>> Ok. The fix for the second problem would be nice to have soon, as
>>>> analogy breaks the build on blackfin for this reason. If it is of any
>>>> help, you can send me a patch for this fix only which I will apply on my
>>>> side while you are working on other changes.
>>>>
>>> I modified the common part of the NI driver so that the PCI code can be
>>> disabled without any compilation issues.
>>>
>>> I made a pull request which contains the fixes.
>> Thanks, but well, the compilation still fails on blackfin:
>> http://sisyphus.hd.free.fr/~gilles/bx/bf537-stamp/2.6.30-bfin-uclinux-gcc-4.1.2/log.html#13
>>
>
> This is because arch/blackfin/include/asm/pci.h does not include
> asm-generic/pci-dma-compat.h in 2.6.30 yet. Upstream fixed this is
> 2.6.31.
>
> So either we patch in some ugliness like below, or I issue a revised
> pipeline patch for 2.6.30.6 which fixes this upstream bug.
Ok. As you wish. Could you also have a look at the bf561 compilation? It
seems rtdm gets undefined references to some rthal_atomic* operations.
http://sisyphus.hd.free.fr/~gilles/bx/bf537-stamp/2.6.31-bfin-uclinux-gcc-4.1.2/log.html#1
--
Gilles.
next prev parent reply other threads:[~2009-12-26 22:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 10:06 [Xenomai-core] Build tests: analogy, blackfin, rtcan and nios2 Gilles Chanteperdrix
2009-12-22 10:43 ` Philippe Gerum
2009-12-22 11:36 ` Jan Kiszka
2009-12-22 11:45 ` Gilles Chanteperdrix
2009-12-22 11:50 ` Wolfgang Grandegger
2009-12-22 11:55 ` Wolfgang Grandegger
2009-12-22 12:30 ` Gilles Chanteperdrix
2009-12-22 12:43 ` Jan Kiszka
2009-12-22 12:46 ` Gilles Chanteperdrix
2009-12-22 13:38 ` Wolfgang Grandegger
2009-12-22 13:10 ` Patrice Kadionik
2009-12-22 14:07 ` Patrice Kadionik
2009-12-23 12:16 ` Gilles Chanteperdrix
2009-12-23 1:03 ` Alexis Berlemont
2009-12-23 12:32 ` Gilles Chanteperdrix
2009-12-26 0:09 ` Alexis Berlemont
2009-12-26 18:09 ` Gilles Chanteperdrix
2009-12-26 18:27 ` Philippe Gerum
2009-12-26 22:54 ` Gilles Chanteperdrix [this message]
2009-12-27 0:22 ` Philippe Gerum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B369415.1090200@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Xenomai-core@domain.hid \
--cc=rpm@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.