Sorry for the late.
On 10/31/07, David Howells <[EMAIL PROTECTED]> wrote:
> > But is there any utility that depends on that uname says mn10300?
>
> autoconf:-)
I forgot again the one as an host environment. :-)
AFAIK, mn10300 series are for embedded systems and I've never heard as
development
Sorry for the late.
On 10/31/07, David Howells [EMAIL PROTECTED] wrote:
But is there any utility that depends on that uname says mn10300?
autoconf:-)
I forgot again the one as an host environment. :-)
AFAIK, mn10300 series are for embedded systems and I've never heard as
development hosts.
I
> Can you guarantee there won't be any non-AM33 variants of mn10300 that need
> supporting? An AM34, perhaps?
>
> So basically, the toolchain name should change from am33 to mn10300 by your
> argument.
Given the "i686" toolchain name is wrong (its actually i686 + cmov) there
is a ton of history
Can you guarantee there won't be any non-AM33 variants of mn10300 that need
supporting? An AM34, perhaps?
So basically, the toolchain name should change from am33 to mn10300 by your
argument.
Given the i686 toolchain name is wrong (its actually i686 + cmov) there
is a ton of history for
Suzuki Takashi <[EMAIL PROTECTED]> wrote:
> But is there any utility that depends on that uname says mn10300?
autoconf:-)
> I know existing developers should learn the arch name change.
> But how many developers?
I don't know. MEI probably does.
> That's the point. They must always be told
On 10/31/07, David Howells <[EMAIL PROTECTED]> wrote:
> > But the arch name change does not affect running kernels on consumer
> > devices.
>
> uname says mn10300.
Oh, I forgot.
But is there any utility that depends on that uname says mn10300?
> > Drastic changes in the directory and file
> They can if they're told so, plus if they've got the CPU docs to
> hand, it should be more obvious. The AM33 is a variant of the
> MN10300 arch as far as I can tell.
Right, there's also the AM30, AM31, AM32, and AM34. Panasonic calls
the whole series the "AM3" or "MN103 series" although they
Suzuki Takashi <[EMAIL PROTECTED]> wrote:
> But the arch name change does not affect running kernels on consumer devices.
uname says mn10300.
> Drastic changes in the directory and file structures will have
> a much greater impact than that.
Like renaming the arch/mn10300 and
On 10/30/07, David Howells <[EMAIL PROTECTED]> wrote:
> > Why don't you use `am33' for the arch name?
>
> History and the fact that 'mn10300' is what MEI called their arch when they
> originally gave us (RH) their kernel. There are kernels already out there
> running on consumer devices for which
Suzuki Takashi <[EMAIL PROTECTED]> wrote:
> Why don't you use `am33' for the arch name?
History and the fact that 'mn10300' is what MEI called their arch when they
originally gave us (RH) their kernel. There are kernels already out there
running on consumer devices for which it is the mn10300
On 10/29/07, David Howells <[EMAIL PROTECTED]> wrote:
> The second patch adds the architecture itself, to be selected by ARCH=mn10300
> on the make command line.
Why don't you use `am33' for the arch name?
Do you have any plans to support am30 (mn10300) or any pre-am33 processor cores?
I know
On 10/29/07, David Howells [EMAIL PROTECTED] wrote:
The second patch adds the architecture itself, to be selected by ARCH=mn10300
on the make command line.
Why don't you use `am33' for the arch name?
Do you have any plans to support am30 (mn10300) or any pre-am33 processor cores?
I know the
Suzuki Takashi [EMAIL PROTECTED] wrote:
Why don't you use `am33' for the arch name?
History and the fact that 'mn10300' is what MEI called their arch when they
originally gave us (RH) their kernel. There are kernels already out there
running on consumer devices for which it is the mn10300
On 10/30/07, David Howells [EMAIL PROTECTED] wrote:
Why don't you use `am33' for the arch name?
History and the fact that 'mn10300' is what MEI called their arch when they
originally gave us (RH) their kernel. There are kernels already out there
running on consumer devices for which it is
Suzuki Takashi [EMAIL PROTECTED] wrote:
But the arch name change does not affect running kernels on consumer devices.
uname says mn10300.
Drastic changes in the directory and file structures will have
a much greater impact than that.
Like renaming the arch/mn10300 and include/asm-mn10300
They can if they're told so, plus if they've got the CPU docs to
hand, it should be more obvious. The AM33 is a variant of the
MN10300 arch as far as I can tell.
Right, there's also the AM30, AM31, AM32, and AM34. Panasonic calls
the whole series the AM3 or MN103 series although they also
On 10/31/07, David Howells [EMAIL PROTECTED] wrote:
But the arch name change does not affect running kernels on consumer
devices.
uname says mn10300.
Oh, I forgot.
But is there any utility that depends on that uname says mn10300?
Drastic changes in the directory and file structures will
Suzuki Takashi [EMAIL PROTECTED] wrote:
But is there any utility that depends on that uname says mn10300?
autoconf:-)
I know existing developers should learn the arch name change.
But how many developers?
I don't know. MEI probably does.
That's the point. They must always be told or
These patches add the MEI/Panasonic MN10300/AM33 architecture to the Linux
kernel.
The first patch makes it possible to suppress AOUT support in the ELF binfmt.
MN10300 does not support the AOUT binfmt, so the ELF binfmt should not be
permitted to go looking for AOUT libraries to load.
The
These patches add the MEI/Panasonic MN10300/AM33 architecture to the Linux
kernel.
The first patch makes it possible to suppress AOUT support in the ELF binfmt.
MN10300 does not support the AOUT binfmt, so the ELF binfmt should not be
permitted to go looking for AOUT libraries to load.
The
20 matches
Mail list logo
