From: Daniel Vetter <daniel@ffwll.ch>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [PATCH] video/fbdev: Always built-in video= cmdline parsing
Date: Wed, 06 Aug 2014 12:48:23 +0000 [thread overview]
Message-ID: <20140806124823.GE8727@phenom.ffwll.local> (raw)
In-Reply-To: <CAMuHMdUmy=PLh_z=D9S=oj2dxG74sXC-3_-7V8PCQgNMLz8ngQ@mail.gmail.com>
On Wed, Aug 06, 2014 at 12:27:32PM +0200, Geert Uytterhoeven wrote:
> On Wed, Aug 6, 2014 at 11:43 AM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > In drm/i915 we want to get at the video= cmdline modes even when we
> > don't have fbdev support enabled, so that users can always override
> > the kernel's initial mode selection.
> >
> > But that gives us a direct depency upon the parsing code in the fbdev
> > subsystem. Since it's so little code just extract these 2 functions
> > and always build them in.
>
> How much is "so little"? Think memory-constrained systems.
>
> You can still build it depending on CONFIG_FB or CONFIG_DRM_I915.
I'll do it as an option selected by FB and DRM then.
>
> > diff --git a/drivers/video/fbdev/core/Makefile b/drivers/video/fbdev/core/Makefile
> > index fa306538dac2..891c1f890e03 100644
> > --- a/drivers/video/fbdev/core/Makefile
> > +++ b/drivers/video/fbdev/core/Makefile
> > @@ -1,4 +1,4 @@
> > -obj-y += fb_notify.o
>
> Oh, this is already unconditional. Who are its users?
Welcome in fbdev-land. Not going to fix this, since my dragon-slaying
sword is already broken.
>
> > +obj-y += fb_notify.o fb_cmdline.o
> > obj-$(CONFIG_FB) += fb.o
> > fb-y := fbmem.o fbmon.o fbcmap.o fbsysfs.o \
> > modedb.o fbcvt.o
> > diff --git a/drivers/video/fbdev/core/fb_cmdline.c b/drivers/video/fbdev/core/fb_cmdline.c
> > new file mode 100644
> > index 000000000000..91503a43213e
> > --- /dev/null
> > +++ b/drivers/video/fbdev/core/fb_cmdline.c
> > @@ -0,0 +1,103 @@
> > +/*
> > + * linux/drivers/video/fb_cmdline.c
> > + *
> > + * Copyright (C) 2014 Intel Corp
> > + *
> > + * This file is subject to the terms and conditions of the GNU General Public
> > + * License. See the file COPYING in the main directory of this archive
> > + * for more details.
> > + *
> > + * Authors:
> > + * Vetter <danie.vetter@ffwll.ch>
> > + */
>
> The above chunk doesn't sound appropriate for extracting existing code...
Well it all horribly predates git history, so no idea who actually wrote
this. I'll copy over the old header on top.
-Daniel
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [PATCH] video/fbdev: Always built-in video= cmdline parsing
Date: Wed, 6 Aug 2014 14:48:23 +0200 [thread overview]
Message-ID: <20140806124823.GE8727@phenom.ffwll.local> (raw)
In-Reply-To: <CAMuHMdUmy=PLh_z=D9S=oj2dxG74sXC-3_-7V8PCQgNMLz8ngQ@mail.gmail.com>
On Wed, Aug 06, 2014 at 12:27:32PM +0200, Geert Uytterhoeven wrote:
> On Wed, Aug 6, 2014 at 11:43 AM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > In drm/i915 we want to get at the video= cmdline modes even when we
> > don't have fbdev support enabled, so that users can always override
> > the kernel's initial mode selection.
> >
> > But that gives us a direct depency upon the parsing code in the fbdev
> > subsystem. Since it's so little code just extract these 2 functions
> > and always build them in.
>
> How much is "so little"? Think memory-constrained systems.
>
> You can still build it depending on CONFIG_FB or CONFIG_DRM_I915.
I'll do it as an option selected by FB and DRM then.
>
> > diff --git a/drivers/video/fbdev/core/Makefile b/drivers/video/fbdev/core/Makefile
> > index fa306538dac2..891c1f890e03 100644
> > --- a/drivers/video/fbdev/core/Makefile
> > +++ b/drivers/video/fbdev/core/Makefile
> > @@ -1,4 +1,4 @@
> > -obj-y += fb_notify.o
>
> Oh, this is already unconditional. Who are its users?
Welcome in fbdev-land. Not going to fix this, since my dragon-slaying
sword is already broken.
>
> > +obj-y += fb_notify.o fb_cmdline.o
> > obj-$(CONFIG_FB) += fb.o
> > fb-y := fbmem.o fbmon.o fbcmap.o fbsysfs.o \
> > modedb.o fbcvt.o
> > diff --git a/drivers/video/fbdev/core/fb_cmdline.c b/drivers/video/fbdev/core/fb_cmdline.c
> > new file mode 100644
> > index 000000000000..91503a43213e
> > --- /dev/null
> > +++ b/drivers/video/fbdev/core/fb_cmdline.c
> > @@ -0,0 +1,103 @@
> > +/*
> > + * linux/drivers/video/fb_cmdline.c
> > + *
> > + * Copyright (C) 2014 Intel Corp
> > + *
> > + * This file is subject to the terms and conditions of the GNU General Public
> > + * License. See the file COPYING in the main directory of this archive
> > + * for more details.
> > + *
> > + * Authors:
> > + * Vetter <danie.vetter@ffwll.ch>
> > + */
>
> The above chunk doesn't sound appropriate for extracting existing code...
Well it all horribly predates git history, so no idea who actually wrote
this. I'll copy over the old header on top.
-Daniel
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-08-06 12:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 8:08 [PATCH] drm: Perform cmdline mode parsing during connector initialisation Daniel Vetter
2014-08-06 9:43 ` [PATCH] video/fbdev: Always built-in video= cmdline parsing Daniel Vetter
2014-08-06 9:43 ` Daniel Vetter
2014-08-06 10:27 ` Geert Uytterhoeven
2014-08-06 10:27 ` Geert Uytterhoeven
2014-08-06 12:48 ` Daniel Vetter [this message]
2014-08-06 12:48 ` Daniel Vetter
2014-08-06 12:05 ` Daniel Vetter
2014-08-06 12:05 ` Daniel Vetter
2014-08-06 12:52 ` [PATCH 1/2] " Daniel Vetter
2014-08-06 12:52 ` Daniel Vetter
2014-08-06 12:52 ` [PATCH 2/2] drm: Perform cmdline mode parsing during connector initialisation Daniel Vetter
2014-09-30 11:40 ` [PATCH 1/2] video/fbdev: Always built-in video= cmdline parsing Tomi Valkeinen
2014-09-30 11:40 ` Tomi Valkeinen
2014-09-30 11:53 ` Daniel Vetter
2014-09-30 11:53 ` Daniel Vetter
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=20140806124823.GE8727@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.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 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.