From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/avrdude: add linux gpio kconfig option
Date: Fri, 19 May 2017 16:48:14 +0200 [thread overview]
Message-ID: <8760gw3ntd.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CANQCQpagwa4KgHS0gw-YL_U2-KUV5_tuFM5a0gqt_1TahN6Vjw@mail.gmail.com> (Matthew Weber's message of "Fri, 19 May 2017 08:58:25 -0500")
>>>>> "Matthew" == Matthew Weber <matthew.weber@rockwellcollins.com> writes:
Hi,
>> Didn't you just agree with Baruch that we could just enable it
>> unconditially and not have a Config.in option for it?
>>
> Not sure we reached a conclusion. I guess the question would be,
> right now in buildroot it doesn't enable this option. So if we by
> default go linux-gpio it disables the legacy options which were the
> previous default (kernel's older then sysfs gpio support)
Do you mean that enabling this driver disables anything else? I don't
see that. The kernel's gpio sysfs interface is close to 10 years old by
now, so I doubt that is an issue.
From the looks of it, the linuxgpio driver seems to be very small
compared to the total size of avrdude, so unconditionally enabling it
sounds sensible to me.
I notice that we are using a fork of avrdude which hasn't really been
updated significantly since 2013 instead of the official one which had a
release in 2016. Any reason we shouldn't be using the official one
instead?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-05-19 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 15:08 [Buildroot] [PATCH v2 1/2] package/avrdude: add linux gpio kconfig option Matt Weber
2017-05-18 15:08 ` [Buildroot] [PATCH v2 2/2] package/avrdude: bump to f8893ccf0aceeff67c45f95ae4e86bc7fbe342aa Matt Weber
2017-05-19 13:14 ` [Buildroot] [PATCH v2 1/2] package/avrdude: add linux gpio kconfig option Peter Korsgaard
2017-05-19 13:58 ` Matthew Weber
2017-05-19 14:39 ` Thomas Petazzoni
2017-05-19 14:48 ` Peter Korsgaard [this message]
2017-05-19 15:01 ` Matthew Weber
2017-05-19 15:40 ` Sam Voss
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=8760gw3ntd.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox