From: fche@redhat.com (Frank Ch. Eigler)
To: "Robert Cragie" <rcc@jennic.com>
Cc: <sid@sources.redhat.com>
Subject: Re: hw-cpu-openrisc
Date: Mon, 23 Dec 2002 08:53:00 -0000 [thread overview]
Message-ID: <o5k7i0y8vi.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <NMEDLDELHPEFHOMFIJBHAEIMCJAA.rcc@jennic.com>
"Robert Cragie" <rcc@jennic.com> writes:
> I'm having a go at piecing the jigsaw together...
Good.
> > The work includes ...
> > - adding sid configury for the openrisc target; see
> > sid/config/sidtargets.m4;
>
> Will something like this be sufficient?
>
> Index: sidtargets.m4
> ===================================================================
> [...]
Looks good.
> > will need autoconf/automake runs throughout
>
> So how do I do this exactly? I don't know much about these utilities, I'm
> afraid. [...]
You really need to bite the bullet and figure out a bit about how they
work. The basics can be accomplished by configuring the sid build
tree (only) with --enable-maintainer-mode, putting the
sources.redhat.com binutils "official" version of autoconf etc. into
your $PATH, touching all the configure.in, Makefile.am files, and
running a build. If you do a grep over configure*/Makefile* files in
the source tree, you'll see the lots of places where these sidtarget*
type configury bits show up.
> > - adding sid configuration file generator pieces to sid/bsp/configrun-sid
>
> Again, I think I can see what to do here, assuming I don't want any 'boards'
> just yet. Would something like this do?
> [...]
Yup, except that if there exists a typical libgloss/newlib port for
openrisc, you can likely go for the plain generic gloss model instead
of requiring an openrisc-specific one.
> [...]
> > - populating sid/component/cgen-cpu/openrisc [...]
>
> This is where I'm getting a little bit unstuck. Looking at the m32r
> subdirectory, I can see the m32r-decode.cxx etc. files which all say they
> are automatically generated by CGEN. But how did they get here? [...]
Each per-cpu Makefile includes commands that run cgen so that the
sid-targeted simulation kernel is emitted in the source directory.
> I presume the additional hand-written files are needed to implement
> the sid interfaces.
Right. It is important to start small and handle only the basic
cases.
> [...] I would really like to have a go at doing this, but I'm
> finding it hard going with lack of documentation at the SID level
> and a huge directory tree. [...]
It's hard to come up with a full recipe. We've all learned by being
talked through the process or figuring it out alone. :-) As soon as
something almost builds/works, the missing bits become pretty obvious.
- FChE
prev parent reply other threads:[~2002-12-23 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 5:27 hw-cpu-openrisc Robert Cragie
2002-12-13 7:40 ` hw-cpu-openrisc Frank Ch. Eigler
2002-12-23 8:08 ` hw-cpu-openrisc Robert Cragie
2002-12-23 8:53 ` Frank Ch. Eigler [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=o5k7i0y8vi.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=rcc@jennic.com \
--cc=sid@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).