From: minux <minux.ma@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Teg2 port on qemu
Date: Tue, 23 Dec 2014 00:18:02 -0500 [thread overview]
Message-ID: <CA+db=n1S2tu=JvGDZ7QASG2cZ3-CJhHBmU39e7iu3kRmSdB8aA@mail.gmail.com> (raw)
In-Reply-To: <CADNhbx3t0xqzMVTh4LNGDZNecgY4UhMZ1r3jxrqJde4G4Ctq0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
On Mon, Dec 22, 2014 at 7:28 PM, Andrés Domínguez <andresdju@gmail.com>
wrote:
> 2014-12-23 0:39 GMT+01:00 minux <minux.ma@gmail.com>:
>
>>
>> On Mon, Dec 22, 2014 at 12:23 PM, Andrés Domínguez <andresdju@gmail.com>
>> wrote:
>>
>>> Has someone run successfully the teg2 port on qemu-system-arm?
>>>
>> I don't think qemu-system-arm supports the tegra2 platform.
>>
>
> I know that it doesn't support tegra2, but it supports cortex-a9 mp, so I
> was dreaming (without
> much hope) that someone had run the teg2 port at "some level", at least
> booting it with
> console support.
>
Unfortunately, although some are using 16550 style UARTs, each ARM SoC has
their
own flavor of UART and the differences are even greater at the ethernet,
lcd, sd/mmc level,
so you can't get a port to a SoC not supported by qemu to run on qemu
without changing
a lot of things.
Linux and freebsd are trying to solve that problem with device trees, but
Plan 9 doesn't have
that. plan9.ini and kernel command line is probably not enough to specify
all the hardware
differences.
[-- Attachment #2: Type: text/html, Size: 2107 bytes --]
prev parent reply other threads:[~2014-12-23 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 17:23 Andrés Domínguez
2014-12-22 23:39 ` minux
2014-12-23 0:28 ` Andrés Domínguez
2014-12-23 5:18 ` minux [this message]
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='CA+db=n1S2tu=JvGDZ7QASG2cZ3-CJhHBmU39e7iu3kRmSdB8aA@mail.gmail.com' \
--to=minux.ma@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).