From: Adrian Bunk <bunk@fs.tum.de>
To: tariq.shureih@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error compiling ieee1394/pcilynx.c (2.5.54)
Date: Thu, 16 Jan 2003 02:57:18 +0100 [thread overview]
Message-ID: <20030116015718.GF2333@fs.tum.de> (raw)
In-Reply-To: <34072.10.10.213.14.1042675870.squirrel@linux.intel.com>
On Wed, Jan 15, 2003 at 04:11:10PM -0800, Tariq Shureih wrote:
>...
> The pcilynx.c driver will not compile giving the following error.
> I enabled I2C bit-bangin options as required by the driver.
>
> Seems that the driver requires porting to 2.5.x since the i2c structures
> and implementation has changed in 2.5.x.
>
> Anyone working on this? I can't proceed with my work not having this
> compile.
Below is the fix (already sent to Ben Collins).
> Thanx
cu
Adrian
--- linux-2.5.54/drivers/ieee1394/pcilynx.c.old 2003-01-03 06:58:52.000000000 +0100
+++ linux-2.5.54/drivers/ieee1394/pcilynx.c 2003-01-03 07:02:47.000000000 +0100
@@ -127,23 +127,20 @@
}
static struct i2c_algo_bit_data bit_data = {
- NULL,
- bit_setsda,
- bit_setscl,
- bit_getsda,
- bit_getscl,
- 5, 5, 100, /* waits, timeout */
+ .setsda = bit_setsda,
+ .setscl = bit_setscl,
+ .getsda = bit_getsda,
+ .getscl = bit_getscl,
+ .udelay = 5,
+ .mdelay = 5,
+ .timeout = 100,
};
static struct i2c_adapter bit_ops = {
- "PCILynx I2C adapter",
- 0xAA, //FIXME: probably we should get an id in i2c-id.h
- NULL,
- NULL,
- NULL,
- NULL,
- bit_reg,
- bit_unreg,
+ .name = "PCILynx I2C adapter",
+ .id = 0xAA, //FIXME: probably we should get an id in i2c-id.h
+ .client_register = bit_reg,
+ .client_unregister = bit_unreg,
};
prev parent reply other threads:[~2003-01-16 1:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 0:11 Error compiling ieee1394/pcilynx.c (2.5.54) Tariq Shureih
2003-01-16 1:57 ` Adrian Bunk [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=20030116015718.GF2333@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tariq.shureih@intel.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