From: "Sébastien Chrétien" <sebastien.chretien.enseirb@gmail.com>
To: benh@kernel.crashing.org
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: [MPC7448] machdep_calls
Date: Mon, 18 Aug 2008 13:35:35 +0200 [thread overview]
Message-ID: <319b0ac50808180435o4a8e5bebr79f86e17ba2fb9af@mail.gmail.com> (raw)
In-Reply-To: <319b0ac50808180422r504a012djb971bf80e819a6d2@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Can somebody explain me the aim of the function "setup_arch" in the
machine_call structure ?
2008/8/18, Sébastien Chrétien <sebastien.chretien.enseirb@gmail.com>:
>
> Ok I am going to copy some examples.
>
> 2008/8/18, Benjamin Herrenschmidt <benh@kernel.crashing.org>:
>>
>> On Mon, 2008-08-18 at 10:45 +0200, Sébastien Chrétien wrote:
>> > Hello,
>> >
>> > I am developping a Linux for my PPC Board. I must write a
>> > define_machine structure (marchdep_calls). Where can I find some
>> > Information about functions of this structure ?
>>
>>
>> It isn't well documented unfortunately. Best is to look at what others
>> do... and then find your way through.
>>
>> I agree somebody should write dome doco one day ... in the meantime,
>> feel free to ask questions here.
>>
>> Cheers,
>> Ben.
>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 1504 bytes --]
next prev parent reply other threads:[~2008-08-18 11:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 8:45 [MPC7448] machdep_calls Sébastien Chrétien
2008-08-18 9:27 ` Benjamin Herrenschmidt
2008-08-18 11:22 ` Sébastien Chrétien
2008-08-18 11:35 ` Sébastien Chrétien [this message]
2008-08-18 12:20 ` Michael Ellerman
2008-08-18 14:17 ` Sébastien Chrétien
2008-08-18 21:39 ` Benjamin Herrenschmidt
2008-08-19 7:00 ` Sébastien Chrétien
2008-08-19 7:27 ` Benjamin Herrenschmidt
2008-08-19 9:23 ` Sébastien Chrétien
2008-08-18 21:11 ` Benjamin Herrenschmidt
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=319b0ac50808180435o4a8e5bebr79f86e17ba2fb9af@mail.gmail.com \
--to=sebastien.chretien.enseirb@gmail.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=benh@kernel.crashing.org \
/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).