Suzuki Takashi <[EMAIL PROTECTED]> wrote:
> I'm very annoyed and a bit surprised to hear they admitted such a big
> change so easily.
Why be annoyed? It's not actually a substantial change.
> You and I know there are consumer devices already out running the am33
> port of the kernel.
Yes, and
Suzuki Takashi [EMAIL PROTECTED] wrote:
I'm very annoyed and a bit surprised to hear they admitted such a big
change so easily.
Why be annoyed? It's not actually a substantial change.
You and I know there are consumer devices already out running the am33
port of the kernel.
Yes, and have
Thank you for your replies.
On 10/31/07, David Howells <[EMAIL PROTECTED]> wrote:
> Anyway, I've discussed this with MEI, and they're willing for some flattening
> to take place.
I'm very annoyed and a bit surprised to hear they admitted such a big
change so easily.
You and I know there are
Thank you for your replies.
On 10/31/07, David Howells [EMAIL PROTECTED] wrote:
Anyway, I've discussed this with MEI, and they're willing for some flattening
to take place.
I'm very annoyed and a bit surprised to hear they admitted such a big
change so easily.
You and I know there are
Suzuki Takashi <[EMAIL PROTECTED]> wrote:
> But people aren't, are they?
On the other hand, these particular header files are of interest to arch
maintainers.
If there are variances between CPUs that mandate different sets of registers
or different usage protocols for equivalent modules, then
Suzuki Takashi [EMAIL PROTECTED] wrote:
But people aren't, are they?
On the other hand, these particular header files are of interest to arch
maintainers.
If there are variances between CPUs that mandate different sets of registers
or different usage protocols for equivalent modules, then you
On 10/31/07, David Howells <[EMAIL PROTECTED]> wrote:
> > Does this mean cpu-am33v3, cpu-am33v4, etc. will be created
> > when a new core comes up?
>
> Yes. Note that the headers in a later one can 'inherit' from those of an
> earlier one simply by #including that earlier one, much like archs do
Suzuki Takashi <[EMAIL PROTECTED]> wrote:
> Does this mean cpu-am33v3, cpu-am33v4, etc. will be created
> when a new core comes up?
Yes. Note that the headers in a later one can 'inherit' from those of an
earlier one simply by #including that earlier one, much like archs do with
asm-generic
On 10/29/07, David Howells <[EMAIL PROTECTED]> wrote:
> diff --git a/Documentation/mn10300/compartmentalisation.txt
> b/Documentation/mn10300/compartmentalisation.txt
(snip)
> + (1) CPU level
> +
> + This involves support for a specific set of registers and instructions
> and
> + some
On 10/29/07, David Howells [EMAIL PROTECTED] wrote:
diff --git a/Documentation/mn10300/compartmentalisation.txt
b/Documentation/mn10300/compartmentalisation.txt
(snip)
+ (1) CPU level
+
+ This involves support for a specific set of registers and instructions
and
+ some very
Suzuki Takashi [EMAIL PROTECTED] wrote:
Does this mean cpu-am33v3, cpu-am33v4, etc. will be created
when a new core comes up?
Yes. Note that the headers in a later one can 'inherit' from those of an
earlier one simply by #including that earlier one, much like archs do with
asm-generic
On 10/31/07, David Howells [EMAIL PROTECTED] wrote:
Does this mean cpu-am33v3, cpu-am33v4, etc. will be created
when a new core comes up?
Yes. Note that the headers in a later one can 'inherit' from those of an
earlier one simply by #including that earlier one, much like archs do with
12 matches
Mail list logo
