From: Nicolas Boichat <nicolas@boichat.ch>
To: adaplas@pol.net, Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Fw: Rivafb I2C problem, new patch
Date: Tue, 13 Jul 2004 11:53:01 +0200 [thread overview]
Message-ID: <1089712381.6181.20.camel@tom> (raw)
In-Reply-To: <200407130958.15483.adaplas@hotpop.com>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
Hello,
Thanks for your answers.
I attached a new patch: I deleted the lines that were commented out.
Best regards,
Nicolas
On Tue, 2004-07-13 at 03:58, Antonino A. Daplas wrote:
> I'm not the maintainer of rivafb but I added the DDC2 support for it. The bus
> was destroyed because there was no use for it after reading the EDID block,
> and fbdev has no interface (yet) to re-read it again.
>
> It doesn't matter to me whether the bus is immediately deleted or not, so the
> patch is fine by me.
>
> Tony
On Tue, 2004-07-13 at 01:43, Greg KH wrote:
> Well, you shouldn't comment out those calls, just delete them.
>
> Other than that, from an i2c standpoint, the patch looks sane, but I
> would check with the maintainer, as there might be some reason they
> delete the bus right after using it.
>
> thanks,
>
> greg k-h
[-- Attachment #2: Type: text/x-patch, Size: 1042 bytes --]
--- linux/drivers/video/riva/fbdev.c.old 2004-07-13 02:05:47.029754640 +0200
+++ linux/drivers/video/riva/fbdev.c 2004-07-13 02:08:25.945966745 +0200
@@ -1773,7 +1773,6 @@
struct riva_par *par = (struct riva_par *) info->par;
int i;
- riva_create_i2c_busses(par);
for (i = par->bus; i >= 1; i--) {
riva_probe_i2c_connector(par, i, &par->EDID);
if (par->EDID) {
@@ -1781,7 +1780,6 @@
break;
}
}
- riva_delete_i2c_busses(par);
#endif
#endif
}
@@ -1933,6 +1931,8 @@
}
#endif /* CONFIG_MTRR */
+ riva_create_i2c_busses((struct riva_par *) info->par);
+
info->fbops = &riva_fb_ops;
info->fix = rivafb_fix;
riva_get_EDID(info, pd);
@@ -1961,6 +1961,7 @@
return 0;
err_out_iounmap_fb:
+ riva_delete_i2c_busses((struct riva_par *) info->par);
iounmap(info->screen_base);
err_out_free_base1:
if (default_par->riva.Architecture == NV_ARCH_03)
@@ -1989,6 +1990,8 @@
if (!info)
return;
+ riva_delete_i2c_busses(par);
+
unregister_framebuffer(info);
#ifdef CONFIG_MTRR
if (par->mtrr.vram_valid)
next prev parent reply other threads:[~2004-07-13 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 23:39 Fw: Rivafb I2C problem, new patch Andrew Morton
2004-07-12 23:43 ` Greg KH
2004-07-13 1:58 ` Antonino A. Daplas
2004-07-13 9:53 ` Nicolas Boichat [this message]
2004-07-13 20:52 ` Antonino A. Daplas
2004-07-13 21:46 ` Nicolas Boichat
2004-07-13 22:02 ` Andrew Morton
2004-07-13 23:45 ` Nicolas Boichat
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=1089712381.6181.20.camel@tom \
--to=nicolas@boichat.ch \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.