All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Krafft <krafft@de.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org,
	openipmi-developer@lists.sourceforge.net,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [Openipmi-developer] [patch 1/1] ipmi: add autosensing of ipmi device on powerpc using device-tree
Date: Mon, 11 Dec 2006 18:20:01 +0100	[thread overview]
Message-ID: <20061211182001.0896b7bd@localhost> (raw)
In-Reply-To: <06260804-0C3C-4A40-9E69-408E77973984@kernel.crashing.org>

Good then, it make things easier for me ;-)
Will send an updated version soon...

Cheers, ck

On Mon, 11 Dec 2006 17:58:36 +0100
Segher Boessenkool <segher@kernel.crashing.org> wrote:

> > If I understood you comments an example OFDT node for IPMI could
> > look like the following:
> >
> > name =3D "ipmi"
> > device_type =3D "ipmi"
> > compatible =3D "ipmi-kcs"
> >
> > reg =3D XXXXXXX8 00000008
> > reg-spacing =3D 4
>=20
> Yeah.
>=20
> > reg-size    =3D 1
> > reg-shift   =3D 0
>=20
> But without these two, they are the default.
>=20
> > Is the "8" of the reg property correct?
>=20
> Sure.  Alternatively, if your device really only claims
> bus cycles targeting the 8-bit regs at xxx8 and xxxC, you
> can say that in the "reg" property.  This doesn't change
> the programming model in the least though.
>=20
> > I'm still worried what happens when we have a BT or SMIC interface
> > an the registers sitting at XXXXXXX4, XXXXXXX6, XXXXXXXA. In this
> > case the reg-spacing property can't be used anymore. Can this
> > happen in reality?
>=20
> I don't think it is allowed.  Either way, the generic Linux IPMI
> code would need changing for this -- let's worry about it later
> (if ever!)
>=20
>=20
> Segher
>=20


--=20
Mit freundlichen Gr=FCssen,
kind regards,

Christian Krafft
IBM Systems & Technology Group,=20
Linux Kernel Development
IT Specialist

  reply	other threads:[~2006-12-11 17:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 16:22 [patch 0/1] ipmi: add autosensing of ipmi device on powerpc using device-tree Christian Krafft
2006-12-07 16:24 ` [patch 1/1] " Christian Krafft
2006-12-08 10:24   ` Heiko Joerg Schick
2006-12-08 17:19   ` [Openipmi-developer] " Corey Minyard
2006-12-11 12:13     ` Christian Krafft
2006-12-08 18:59   ` Corey Minyard
2006-12-08 19:49     ` Arnd Bergmann
2006-12-08 22:50     ` Benjamin Herrenschmidt
2006-12-09  0:00       ` Arnd Bergmann
2006-12-09  0:07         ` Corey Minyard
2006-12-09 11:44           ` Arnd Bergmann
2006-12-10 18:42             ` Heiko J Schick
2006-12-11 10:11               ` Arnd Bergmann
2006-12-11 13:01                 ` Heiko J Schick
2006-12-11 13:37                   ` Segher Boessenkool
2006-12-11 13:18               ` Segher Boessenkool
2006-12-11 14:25                 ` Arnd Bergmann
2006-12-11 16:28                   ` Heiko J Schick
2006-12-11 16:58                     ` Segher Boessenkool
2006-12-11 17:20                       ` Christian Krafft [this message]
2006-12-11 16:54                   ` Segher Boessenkool
2006-12-09  2:14         ` Benjamin Herrenschmidt
2006-12-09  9:46         ` Segher Boessenkool
2006-12-09 11:46           ` Arnd Bergmann
2006-12-08  0:41 ` [patch 0/1] " Paul Mackerras
2006-12-08 14:04   ` Arnd Bergmann
2006-12-08 17:17     ` [Openipmi-developer] " Corey Minyard

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=20061211182001.0896b7bd@localhost \
    --to=krafft@de.ibm.com \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    --cc=segher@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 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.