From: adaplas@hotpop.com (Antonino A. Daplas)
To: lm-sensors@vger.kernel.org
Subject: Who should I write to about this OOPS in 2,6,11-mm3?
Date: Thu, 19 May 2005 06:25:43 +0000 [thread overview]
Message-ID: <200503162346.28272.adaplas@hotpop.com> (raw)
In-Reply-To: <20050315050746.GB13009@kroah.com>
On Wednesday 16 March 2005 17:54, Jean Delvare wrote:
> Hi Mike, Antonio & all,
>
> > I narrowed the problem down.
> > In the following scenario, the OOPS occurs:
> > CONFIG_I2C=y
> > CONFIG_FB_NVIDIA=y
> > CONFIG_FB_NVIDIA_I2C=y
> >
> > If CONFIG_I2C is changed to build as a module, no crash occurs.
>
> Hardly relevant, since this means CONFIG_FB_NVIDIA!=y as well.
>
> > If CONFIG_FB_NVIDIA_I2C is not set, no crash occurs.
> > If CONFIG_FB_NVIDIA is changed to build as a module, no crash occurs.
>
> I guess the driver won't auto-load, so you should try to modprobe it
> afterwards. Maybe it'll crash as well then.
>
> Mike, can you please provide a decoded oops? There's not much we can do
> without that.
>
> I wonder if this problem could be related to this one:
> http://bugme.osdl.org/show_bug.cgi?idC47
>
> This too is a bit-banging I2C adapter, part of a framebuffer driver
> (savage there instead of nv here).
>
> Antonio, any idea? You wrote both drivers recently.
>
> I'm rather ignorant when it comes to IRQs so I'm not sure I can really
> help.
>
I've only seen the savage bug report. Yes, unfortunately, this is the
case of 2 drivers attempting to control a single device since the savagefb
and the i2c prosavage drivers will attempt to ioremap the same mmio region.
If you need the i2c prosavage bus, then savagefb must be completely
disabled, as setting CONFIG_FB_SAVAGE_I2C to n will not help. If both
savagefb and i2c are needed, then you just have to use the i2c bus
registered by savagefb.
And yes, there is code duplication, but unfortunately savagefb cannot use
the i2c-prosavage bus since one of them will fail to acquire the io regions.
I haven't seen the nvidiafb report, but it is probably something similar.
This is similar to the fbdev/DRM problem of who owns the device. We can
also throw in i2c bus drivers in the mix, at least for VGA devices. Perhaps a
low-level VGA driver (as proposed by Alan Cox) will be needed to resolve
this problem.
Tony
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:25 Who should I write to about this OOPS in 2,6,11-mm3? Greg KH
2005-05-19 6:25 ` Antonino A. Daplas [this message]
2005-05-19 6:25 ` Antonino A. Daplas
2005-05-19 6:25 ` Antonino A. Daplas
[not found] ` <20050317154226.24c1f8f8.akpm@osdl.org>
[not found] ` <200503180754.21258.adaplas@hotpop.com>
2005-03-22 2:40 ` Andrew Morton
2005-03-22 2:59 ` Miles Lane
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Antonino A. Daplas
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Antonino A. Daplas
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Antonino A. Daplas
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Andrew Morton
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Andrew Morton
2005-05-19 6:25 ` Andrew Morton
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Andrew Morton
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Andrew Morton
2005-05-19 6:25 ` Miles Lane
2005-05-19 6:25 ` Andrew Morton
2005-05-26 9:05 ` [lm-sensors] Re: Who should I write to about this OOPS in 2, 6, Andrew Morton
2005-05-26 9:05 ` Greg KH
2005-05-26 9:05 ` Miles Lane
2005-05-26 9:05 ` Andrew Morton
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=200503162346.28272.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=lm-sensors@vger.kernel.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.