From: Hartvig Ekner <hartvige@mips.com>
To: dpchrist@holgerdanske.com (David Christensen)
Cc: linux-mips@oss.sgi.com
Subject: Re: Fw: hello
Date: Wed, 20 Mar 2002 09:59:40 +0100 (MET) [thread overview]
Message-ID: <200203200859.JAA10886@copsun18.mips.com> (raw)
In-Reply-To: <017701c1cf99$a7d9a890$0b01a8c0@w2k30g> from "David Christensen" at Mar 19, 2002 02:55:22 PM
Hi David,
David Christensen writes:
>
> linux-mips@oss.sgi.com:
>
> Thank you all for your replies. :-)
>
>
> Hartvig Ekner <hartvige@mips.com> wrote:
> >> 2. What is the preferred host OS...
> > We use Linux/x86 for kernel compiles,
>
> Which Linux distribution does MIPS use? Since I'm going to be working
> on an Atlas board using software from MIPS, I would like to match things
> up exactly.
Internally for development we use H.J's RedHat 7.1/MIPS miniport.
Ready-to-go kernel images and installation instructions (via NFS or
CDROM) for Atlas and Malta boards can be found on ftp.mips.com.
> As an aside, is anybody using a VMware virtual machine for their
> development host?
>
> > and native compile for apps.
>
> OK that sounds like a safe bet.
>
> >> 3. What is the preferred toolchain...
> > This is what we use for cross Kernel compiles (toolchain from oss):
> >
> > /home/hartvige> gcc -v
> > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
> > gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-85)
>
> Hmmm. That looks like a native i386 compiler. I'm surprised its not
> something like "mips-elf-gcc".
Sorry - I ran the command in the wrong window :-)
For kernel cross compilation we use the following binary RPM's (LE shown only):
binutils-mipsel-linux-2.9.5-3
egcs-mipsel-linux-1.1.2-4
They can be found on:
ftp://oss.sgi.com/pub/linux/mips/crossdev/i386-linux/mipsel-linux/
> I'll assume the cross-compile toolchain was built per
> http://oss.sgi.com/mips/mips-howto.html section 10.
>
> >> 4. Is MIPS Linux self-hosted?
> > Yes. Even without workstations, you could use MIPS or Algo development
> > boards for self-hosted development (which is what we do - primarily
> > Malta boards).
>
> Good. :-)
>
> >> 5. Can you do native development on MIPS Linux?
> > Yes.
>
> Good. :-)
>
> >> 6. Does MIPS Linux support sound (oss or alsa) on any platform?
> >> Does it support sound on MIPS Atlas?
> > Yes. Plug in a Creative SB card, based on the Ensoniq chip and
> > enable the es1371.c in the kernel compile. Works both LE & BE, and
> > with apps like madplay (mp3) and mplayer (mpeg4).
>
> Great! :-)
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Hartvig Ekner <hartvige@mips.com>
To: David Christensen <dpchrist@holgerdanske.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Fw: hello
Date: Wed, 20 Mar 2002 09:59:40 +0100 (MET) [thread overview]
Message-ID: <200203200859.JAA10886@copsun18.mips.com> (raw)
Message-ID: <20020320085940.K8hwdPLfYndiWWxmc_DSGsxbtuC9pLcbJ1U1We6bDp4@z> (raw)
In-Reply-To: <017701c1cf99$a7d9a890$0b01a8c0@w2k30g> from "David Christensen" at Mar 19, 2002 02:55:22 PM
Hi David,
David Christensen writes:
>
> linux-mips@oss.sgi.com:
>
> Thank you all for your replies. :-)
>
>
> Hartvig Ekner <hartvige@mips.com> wrote:
> >> 2. What is the preferred host OS...
> > We use Linux/x86 for kernel compiles,
>
> Which Linux distribution does MIPS use? Since I'm going to be working
> on an Atlas board using software from MIPS, I would like to match things
> up exactly.
Internally for development we use H.J's RedHat 7.1/MIPS miniport.
Ready-to-go kernel images and installation instructions (via NFS or
CDROM) for Atlas and Malta boards can be found on ftp.mips.com.
> As an aside, is anybody using a VMware virtual machine for their
> development host?
>
> > and native compile for apps.
>
> OK that sounds like a safe bet.
>
> >> 3. What is the preferred toolchain...
> > This is what we use for cross Kernel compiles (toolchain from oss):
> >
> > /home/hartvige> gcc -v
> > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
> > gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-85)
>
> Hmmm. That looks like a native i386 compiler. I'm surprised its not
> something like "mips-elf-gcc".
Sorry - I ran the command in the wrong window :-)
For kernel cross compilation we use the following binary RPM's (LE shown only):
binutils-mipsel-linux-2.9.5-3
egcs-mipsel-linux-1.1.2-4
They can be found on:
ftp://oss.sgi.com/pub/linux/mips/crossdev/i386-linux/mipsel-linux/
> I'll assume the cross-compile toolchain was built per
> http://oss.sgi.com/mips/mips-howto.html section 10.
>
> >> 4. Is MIPS Linux self-hosted?
> > Yes. Even without workstations, you could use MIPS or Algo development
> > boards for self-hosted development (which is what we do - primarily
> > Malta boards).
>
> Good. :-)
>
> >> 5. Can you do native development on MIPS Linux?
> > Yes.
>
> Good. :-)
>
> >> 6. Does MIPS Linux support sound (oss or alsa) on any platform?
> >> Does it support sound on MIPS Atlas?
> > Yes. Plug in a Creative SB card, based on the Ensoniq chip and
> > enable the es1371.c in the kernel compile. Works both LE & BE, and
> > with apps like madplay (mp3) and mplayer (mpeg4).
>
> Great! :-)
>
>
next prev parent reply other threads:[~2002-03-20 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-19 22:55 Fw: hello David Christensen
2002-03-19 22:55 ` David Christensen
2002-03-20 6:39 ` Karsten Merker
2002-03-20 8:59 ` Hartvig Ekner [this message]
2002-03-20 8:59 ` Hartvig Ekner
2002-03-20 17:38 ` Ralf Baechle
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=200203200859.JAA10886@copsun18.mips.com \
--to=hartvige@mips.com \
--cc=dpchrist@holgerdanske.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