Re: [PATCH] Export symbol from I2C eeprom driver
From: Greg KH (greg_at_kroah.com)
Date: 01/11/05
- Previous message: Pavel Machek: "Re: Screwy clock after apm suspend"
- In reply to: Jon Smirl: "Re: [PATCH] Export symbol from I2C eeprom driver"
- Next in thread: Jon Smirl: "Re: [PATCH] Export symbol from I2C eeprom driver"
- Reply: Jon Smirl: "Re: [PATCH] Export symbol from I2C eeprom driver"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 10 Jan 2005 15:47:26 -0800 To: Jon Smirl <jonsmirl@gmail.com>
On Sat, Jan 08, 2005 at 07:14:48PM -0500, Jon Smirl wrote:
> On Sat, 8 Jan 2005 14:27:19 -0800, Greg KH <greg@kroah.com> wrote:
> > And why do you need the eeprom driver for the radeon driver to work
> > properly?
>
> In the new radeon driver at hotplug time a user space app reads the
> DDC from the monitor and sets the list of valid modes into the driver.
> The radeon driver includes an I2C driver. The eeprom driver finds the
> radeon DDC ROMs and makes them visible to the userspace driver through
> sysfs. I could add code to the radeon driver to export the DDC ROMs to
> sysfs but the eeprom driver works fine.
>
> I don't want to load the driver from the script because the radeon
> driver is creating a sysfs link into the eeprom directory from the
> radeon one.
How are you getting the kobject to the eeprom directory from the radeon
driver?
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Pavel Machek: "Re: Screwy clock after apm suspend"
- In reply to: Jon Smirl: "Re: [PATCH] Export symbol from I2C eeprom driver"
- Next in thread: Jon Smirl: "Re: [PATCH] Export symbol from I2C eeprom driver"
- Reply: Jon Smirl: "Re: [PATCH] Export symbol from I2C eeprom driver"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
