From: "kjlin" <kj.lin@viditec-netmedia.com.tw>
To: "Joe deBlaquiere" <jadb@redhat.com>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: Does linux support for microprocessor without MMU?
Date: Mon, 26 Feb 2001 17:17:13 +0800 [thread overview]
Message-ID: <037601c09fd4$e81ef540$056aaac0@kjlin> (raw)
In-Reply-To: 3A95F83D.9030600@redhat.com
Is the uClibc/uC-glibc platform dependent??
Can we use the "normal linux glibc" instead of uClibc/uC-glibc when running
uClinux??
As to object file format, is it real necessary to modify the elf2flt
program?
On the other hand, there is an isssue which confuses me.
That is, i had already got a cross-compiler for compiling the "normal linux"
kernel used.
Should i need to remake a cross-compiler to compile the uClinux kernel and
applications?
Thanks.
----- Original Message -----
From: "Joe deBlaquiere" <jadb@redhat.com>
To: "Geert Uytterhoeven" <Geert.Uytterhoeven@sonycom.com>
Cc: "Crossfire" <xfire@xware.cx>; "kjlin" <kj.lin@viditec-netmedia.com.tw>;
<linux-mips@oss.sgi.com>
Sent: Friday, February 23, 2001 1:42 PM
Subject: Re: Does linux support for microprocessor without MMU?
> Geert Uytterhoeven wrote:
>
> > On Wed, 21 Feb 2001, Joe deBlaquiere wrote:
> >
> >>
> >> There isn't (yet) support for MIPS on uClinux.
> >
> >
> > But it can't be that hard to add support for it...
> >
> Porting the kernel isn't much worse than any other architectural port.
> Of course that's only a part of the story, since you'll need to port the
> C library (uClibc/uC-glibc) and you will have to play around with the
> object file format to make it work with FLAT binaries... If you're
> serious about doing uClinux you can find a somewhat cryptic article on
> porting to uClinux at:
>
> http://www.redhat.com/embedded/technologies/resources
>
> --
> Joe
WARNING: multiple messages have this Message-ID (diff)
From: "kjlin" <kj.lin@viditec-netmedia.com.tw>
To: Joe deBlaquiere <jadb@redhat.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Does linux support for microprocessor without MMU?
Date: Mon, 26 Feb 2001 17:17:13 +0800 [thread overview]
Message-ID: <037601c09fd4$e81ef540$056aaac0@kjlin> (raw)
Message-ID: <20010226091713.IS6aylu710QqX7zw_WAHZKeeYgWG098gGctAsLgnc6w@z> (raw)
In-Reply-To: 3A95F83D.9030600@redhat.com
Is the uClibc/uC-glibc platform dependent??
Can we use the "normal linux glibc" instead of uClibc/uC-glibc when running
uClinux??
As to object file format, is it real necessary to modify the elf2flt
program?
On the other hand, there is an isssue which confuses me.
That is, i had already got a cross-compiler for compiling the "normal linux"
kernel used.
Should i need to remake a cross-compiler to compile the uClinux kernel and
applications?
Thanks.
----- Original Message -----
From: "Joe deBlaquiere" <jadb@redhat.com>
To: "Geert Uytterhoeven" <Geert.Uytterhoeven@sonycom.com>
Cc: "Crossfire" <xfire@xware.cx>; "kjlin" <kj.lin@viditec-netmedia.com.tw>;
<linux-mips@oss.sgi.com>
Sent: Friday, February 23, 2001 1:42 PM
Subject: Re: Does linux support for microprocessor without MMU?
> Geert Uytterhoeven wrote:
>
> > On Wed, 21 Feb 2001, Joe deBlaquiere wrote:
> >
> >>
> >> There isn't (yet) support for MIPS on uClinux.
> >
> >
> > But it can't be that hard to add support for it...
> >
> Porting the kernel isn't much worse than any other architectural port.
> Of course that's only a part of the story, since you'll need to port the
> C library (uClibc/uC-glibc) and you will have to play around with the
> object file format to make it work with FLAT binaries... If you're
> serious about doing uClinux you can find a somewhat cryptic article on
> porting to uClinux at:
>
> http://www.redhat.com/embedded/technologies/resources
>
> --
> Joe
next prev parent reply other threads:[~2001-02-26 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 1:26 Does linux support for microprocessor without MMU? kjlin
2001-02-22 1:26 ` kjlin
2001-02-22 2:36 ` Crossfire
2001-02-22 4:15 ` Joe deBlaquiere
2001-02-22 6:53 ` Geert Uytterhoeven
2001-02-23 5:42 ` Joe deBlaquiere
2001-02-26 9:17 ` kjlin [this message]
2001-02-26 9:17 ` kjlin
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='037601c09fd4$e81ef540$056aaac0@kjlin' \
--to=kj.lin@viditec-netmedia.com.tw \
--cc=jadb@redhat.com \
--cc=linux-mips@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox