All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: oops in i2c-rpx.c !
Date: Sun, 23 Nov 2003 15:40:25 +0100	[thread overview]
Message-ID: <3FC0C6D9.8020203@imc-berlin.de> (raw)

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

Hi there,

the attached trival patch fixes a problem when using i2c-rpx.c without applying
the "microcode relocation patch".

Thanks.

BTW: Why is this driver not in linuxppc-2.4 but in linuxppc_2_4_devel?

--
Steven Scholz

imc Measurement & Control               imc Meßsysteme GmbH
Voltastr. 5                             Voltastr. 5
13355 Berlin                            13355 Berlin
Germany                                 Deutschland
fon: +49 30 467090-0                    Tel: 030 / 467090-0
fax: +49 30 4631576                     fax: 030 / 4631576


[-- Attachment #2: i2c-rpx.patch --]
[-- Type: text/plain, Size: 632 bytes --]

Index: drivers/i2c/i2c-rpx.c
===================================================================
RCS file: /cvsroot/linuxppc_2_4_devel/drivers/i2c/i2c-rpx.c,v
retrieving revision 1.2
diff -u -r1.2 i2c-rpx.c
--- drivers/i2c/i2c-rpx.c	2003/10/30 00:32:55	1.2
+++ drivers/i2c/i2c-rpx.c	2003/11/23 14:37:11
@@ -35,10 +35,12 @@

 	data->iip = (iic_t *)&cp->cp_dparam[PROFF_IIC];

+#ifdef USE_IIC_PATCH
 	/* Check for and use a microcode relocation patch.
 	*/
 	if ((data->reloc = data->iip->iic_rpbase))
 		data->iip = (iic_t *)&cp->cp_dpmem[data->iip->iic_rpbase];
+#endif

 	data->i2c = (i2c8xx_t *)&(immap->im_i2c);
 	data->cp = cp;

                 reply	other threads:[~2003-11-23 14:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3FC0C6D9.8020203@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=linuxppc-embedded@lists.linuxppc.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.