Hannes Mayer wrote:
Philippe Gerum wrote:
[...]
The surprise is that xeno_native is statically built-in by default.
You can change that selecting the proper tristate position in the
kernel config for the native skin.
So everything (even the 16550 driver) is compiled in by default ?
I didn't
Hannes Mayer wrote:
Wolfgang Grandegger wrote:
[...]
I have realized the same error building out of the source tree for
PowerPC. The problem is, that the link is pointing to itself. Apart
from that, the ksrc part works fine (at least I can boot the ipipe
kernel).
If I remove the sym-link a
Philippe Gerum wrote:
[...]
The surprise is that xeno_native is statically built-in by default. You
can change that selecting the proper tristate position in the kernel
config for the native skin.
So everything (even the 16550 driver) is compiled in by default ?
I didn't look that closely last
Wolfgang Grandegger wrote:
[...]
I have realized the same error building out of the source tree for
PowerPC. The problem is, that the link is pointing to itself. Apart from
that, the ksrc part works fine (at least I can boot the ipipe kernel).
If I remove the sym-link and copy .svn/text-base/s
Hannes Mayer wrote:
Philippe Gerum wrote:
[...]
The surprise is that xeno_native is statically built-in by default.
You can change that selecting the proper tristate position in the
kernel config for the native skin.
So everything (even the 16550 driver) is compiled in by default ?
I didn't
Hannes Mayer wrote:
Wolfgang Grandegger wrote:
[...]
I have realized the same error building out of the source tree for
PowerPC. The problem is, that the link is pointing to itself. Apart
from that, the ksrc part works fine (at least I can boot the ipipe
kernel).
If I remove the sym-link a
Philippe Gerum wrote:
[...]
The surprise is that xeno_native is statically built-in by default. You
can change that selecting the proper tristate position in the kernel
config for the native skin.
So everything (even the 16550 driver) is compiled in by default ?
I didn't look that closely last
Wolfgang Grandegger wrote:
[...]
I have realized the same error building out of the source tree for
PowerPC. The problem is, that the link is pointing to itself. Apart from
that, the ksrc part works fine (at least I can boot the ipipe kernel).
If I remove the sym-link and copy .svn/text-base/s
Philippe Gerum wrote:
Hannes Mayer wrote:
Ciao Philippe!
prepare-kernel.sh works well - I'd suggest to ask the user for
the 3 needed parameters, instead of supplying them as parameters.
e.g.
# scripts/prepare-kernel.sh
Linux directory: [default: /usr/src/linux] :
Adeos-patch: [default: none] :
> Out of the source tree ?
> I've got everything in /usr/src/xenomai-2.1/ and in this
> directory I did: # ./configure
> # make
>
> Or do you mean in /usr/src/xenomai-2.1/src/ ?
> If the latter: I'd not enforce this as the standard method,
> since people are accustomed to do ./configure and make in
Ciao Philippe!
> Try building out of the source tree; it's something I'm likely going to
> enforce anyway.
Out of the source tree ?
I've got everything in /usr/src/xenomai-2.1/ and in this directory I did:
# ./configure
# make
Or do you mean in /usr/src/xenomai-2.1/src/ ?
If the latter: I'd not
Hannes Mayer wrote:
Ciao Philippe!
prepare-kernel.sh works well - I'd suggest to ask the user for
the 3 needed parameters, instead of supplying them as parameters.
e.g.
# scripts/prepare-kernel.sh
Linux directory: [default: /usr/src/linux] :
Adeos-patch: [default: none] :
Architecture: [default:
Philippe Gerum wrote:
Hannes Mayer wrote:
Ciao Philippe!
prepare-kernel.sh works well - I'd suggest to ask the user for
the 3 needed parameters, instead of supplying them as parameters.
e.g.
# scripts/prepare-kernel.sh
Linux directory: [default: /usr/src/linux] :
Adeos-patch: [default: none] :
> Out of the source tree ?
> I've got everything in /usr/src/xenomai-2.1/ and in this
> directory I did: # ./configure
> # make
>
> Or do you mean in /usr/src/xenomai-2.1/src/ ?
> If the latter: I'd not enforce this as the standard method,
> since people are accustomed to do ./configure and make in
Ciao Philippe!
> Try building out of the source tree; it's something I'm likely going to
> enforce anyway.
Out of the source tree ?
I've got everything in /usr/src/xenomai-2.1/ and in this directory I did:
# ./configure
# make
Or do you mean in /usr/src/xenomai-2.1/src/ ?
If the latter: I'd not
Hannes Mayer wrote:
Ciao Philippe!
prepare-kernel.sh works well - I'd suggest to ask the user for
the 3 needed parameters, instead of supplying them as parameters.
e.g.
# scripts/prepare-kernel.sh
Linux directory: [default: /usr/src/linux] :
Adeos-patch: [default: none] :
Architecture: [default:
Ciao Philippe!
prepare-kernel.sh works well - I'd suggest to ask the user for
the 3 needed parameters, instead of supplying them as parameters.
e.g.
# scripts/prepare-kernel.sh
Linux directory: [default: /usr/src/linux] :
Adeos-patch: [default: none] :
Architecture: [default: i386]
...or somethi
Ciao Philippe!
prepare-kernel.sh works well - I'd suggest to ask the user for
the 3 needed parameters, instead of supplying them as parameters.
e.g.
# scripts/prepare-kernel.sh
Linux directory: [default: /usr/src/linux] :
Adeos-patch: [default: none] :
Architecture: [default: i386]
...or somethi
A dev branch toward v2.1 has been created. It features a new build system so
that Xenomai now follows a split source model, decoupling the kernel space
support from the user-space libraries used in accessing the former.
It's work in progress, and there is still a lot of things to be done in o
A dev branch toward v2.1 has been created. It features a new build system so
that Xenomai now follows a split source model, decoupling the kernel space
support from the user-space libraries used in accessing the former.
It's work in progress, and there is still a lot of things to be done in o
20 matches
Mail list logo