From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] fbset: Add option to install /etc/fb.modes
Date: Wed, 7 Aug 2019 17:05:46 +0200 [thread overview]
Message-ID: <20190807150546.twfm2hcvg2idj5r6@pengutronix.de> (raw)
In-Reply-To: <CABDcava7S_aoYFroE=WaHuMbNO30ewsHZokVw6k0X9Tkfu=_vw@mail.gmail.com>
On Wed, Aug 07, 2019 at 04:22:03PM +0200, Guillermo Rodriguez Garcia wrote:
> El mié., 7 ago. 2019 a las 14:26, Michael Olbrich (<m.olbrich@pengutronix.de>)
> escribió:
> > On Mon, Aug 05, 2019 at 10:18:42AM +0200, Guillermo Rodríguez wrote:
> > > Signed-off-by: Guillermo Rodriguez <guille.rodriguez@gmail.com>
> > > ---
> > > rules/fbset.in | 14 ++++++++++++--
> > > rules/fbset.make | 4 +++-
> > > 2 files changed, 15 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/rules/fbset.in b/rules/fbset.in
> > > index c2122c51b..64dd9ec55 100644
> > > --- a/rules/fbset.in
> > > +++ b/rules/fbset.in
> > > @@ -1,11 +1,21 @@
> > > ## SECTION=multimedia_framebuffer
> > >
> > > -config FBSET
> > > +menuconfig FBSET
> > > tristate
> > > - prompt "fbset"
> > > + prompt "fbset "
> > > select HOST_FLEX
> > > help
> > > fbset is a system utility to show or change the settings
> > > of the frame buffer device. The frame buffer device pro-
> > > vides a simple and unique interface to access different
> > > kinds of graphic displays.
> > > +
> > > +if FBSET
> > > +
> > > +config FBSET_FBMODES
> > > + bool
> > > + prompt "install /etc/fb.modes"
> > > + help
> > > + Install /etc/fb.modes file.
> > > +
> > > +endif
> > > diff --git a/rules/fbset.make b/rules/fbset.make
> > > index 0d34d8959..955480b21 100644
> > > --- a/rules/fbset.make
> > > +++ b/rules/fbset.make
> > > @@ -45,7 +45,9 @@ $(STATEDIR)/fbset.targetinstall:
> > > @$(call install_fixup, fbset,DESCRIPTION,missing)
> > >
> > > @$(call install_copy, fbset, 0, 0, 0755, -, /usr/sbin/fbset)
> > > -
> > > +ifdef PTXCONF_FBSET_FBMODES
> > > + @$(call install_alternative, fbset, 0, 0, 0644, /etc/fb.modes)
> > > +endif
> >
> > Hmmm, I don't like options that are broken by default.
> >
>
> OK, although this is disabled by default. I assume that users that enable
> it have a valid fb.modes file that they want to include..
I do some "enable everything" testing and I prefer to avoid exceptions.
> > Please add a default file in projectroot/.
> >
>
> fb modes (timings specifically) are hardware-specific. Is it OK if I add a
> default file with no modes defined? (I can e.g. add a comment saying that
> it is a placeholder)
If that has the same effect as no config, then it's perfect. Of if it fails
with some meaningful error at runtime it's also ok.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-08-07 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 8:18 Guillermo Rodríguez
2019-08-07 12:25 ` Michael Olbrich
2019-08-07 14:22 ` Guillermo Rodriguez Garcia
2019-08-07 15:05 ` Michael Olbrich [this message]
2019-08-08 16:03 ` [ptxdist] [PATCH v2] " Guillermo Rodríguez
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=20190807150546.twfm2hcvg2idj5r6@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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