All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: "Sébastien Chrétien" <sebastien.chretien.enseirb@gmail.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: [MPC7448] machdep_calls
Date: Mon, 18 Aug 2008 22:20:04 +1000	[thread overview]
Message-ID: <1219062004.7946.5.camel@localhost> (raw)
In-Reply-To: <319b0ac50808180435o4a8e5bebr79f86e17ba2fb9af@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

On Mon, 2008-08-18 at 13:35 +0200, Sébastien Chrétien wrote:
> Can somebody explain me the aim of the function  "setup_arch" in the
> machine_call structure ?

Is this MPC7448 anything like an mpc7448hpc2 ?

If so maybe you should start by looking at the code for it in:

arch/powerpc/platforms/embedded6xx/mpc7448_hpc2.c

Even if it's not related, that will give you some idea of what the
callbacks are for.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-08-18 12:20 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
2008-08-18 12:20       ` Michael Ellerman [this message]
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=1219062004.7946.5.camel@localhost \
    --to=michael@ellerman.id.au \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=sebastien.chretien.enseirb@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.