All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Dave Airlie <airlied@gmail.com>,
	torvalds@linux-foundation.org, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, gregkh@linuxfoundation.org,
	Daniel Vetter <daniel@ffwll.ch>,
	mcgrof@kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.sf.net, netdev@vger.kernel.org,
	linux-wireless@vger.kernel.org, alsa-devel@alsa-project.org,
	linux-media@vger.kernel.org, linux-block@vger.kernel.org,
	Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH] docs: driver-api: firmware: add driver firmware guidelines.
Date: Mon, 18 Jul 2022 15:04:14 -0700	[thread overview]
Message-ID: <20220718150414.1767bbd8@kernel.org> (raw)
In-Reply-To: <97e5afd3-77a3-2227-0fbf-da2f9a41520f@leemhuis.info>

On Mon, 18 Jul 2022 11:33:11 +0200 Thorsten Leemhuis wrote:
> > If the hardware isn't
> > +  enabled by default or under development,  
> 
> Wondering if it might be better to drop the "or under development", as
> the "enabled by default" is the main part afaics. Maybe something like
> "If support for the hardware is normally inactive (e.g. has to be
> enabled manually by a kernel parameter)" would be better anyway.

It's a tricky one, I'd say something like you can break the FW ABI
"until HW becomes available for public consumption" or such.
I'm guessing what we're after is letting people break the compatibility
in early stages of the product development cycles. Pre-silicon and
bring up, but not after there are products on the market?

WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: linux-wireless@vger.kernel.org, alsa-devel@alsa-project.org,
	linux-doc@vger.kernel.org, Dave Airlie <airlied@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	dri-devel@lists.sf.net, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org, mcgrof@kernel.org,
	netdev@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
	gregkh@linuxfoundation.org, Dave Airlie <airlied@redhat.com>,
	torvalds@linux-foundation.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] docs: driver-api: firmware: add driver firmware guidelines.
Date: Mon, 18 Jul 2022 15:04:14 -0700	[thread overview]
Message-ID: <20220718150414.1767bbd8@kernel.org> (raw)
In-Reply-To: <97e5afd3-77a3-2227-0fbf-da2f9a41520f@leemhuis.info>

On Mon, 18 Jul 2022 11:33:11 +0200 Thorsten Leemhuis wrote:
> > If the hardware isn't
> > +  enabled by default or under development,  
> 
> Wondering if it might be better to drop the "or under development", as
> the "enabled by default" is the main part afaics. Maybe something like
> "If support for the hardware is normally inactive (e.g. has to be
> enabled manually by a kernel parameter)" would be better anyway.

It's a tricky one, I'd say something like you can break the FW ABI
"until HW becomes available for public consumption" or such.
I'm guessing what we're after is letting people break the compatibility
in early stages of the product development cycles. Pre-silicon and
bring up, but not after there are products on the market?

  reply	other threads:[~2022-07-18 22:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  7:21 [PATCH] docs: driver-api: firmware: add driver firmware guidelines Dave Airlie
2022-07-18  7:21 ` Dave Airlie
2022-07-18  7:21 ` Dave Airlie
2022-07-18  9:33 ` Thorsten Leemhuis
2022-07-18  9:33   ` Thorsten Leemhuis
2022-07-18 22:04   ` Jakub Kicinski [this message]
2022-07-18 22:04     ` Jakub Kicinski
2022-07-19  0:33     ` Dave Airlie
2022-07-19  0:33       ` Dave Airlie
2022-07-19  0:33       ` Dave Airlie
2022-07-18 17:54 ` Rodrigo Vivi
2022-07-18 17:54   ` Rodrigo Vivi
2022-07-19  0:29   ` Dave Airlie
2022-07-19  0:29     ` Dave Airlie
2022-07-19  0:29     ` Dave Airlie
2022-07-19 14:49     ` Pierre-Louis Bossart
2022-07-19 14:49       ` Pierre-Louis Bossart
2022-07-18 22:00 ` Luis Chamberlain
2022-07-18 22:00   ` Luis Chamberlain
  -- strict thread matches above, loose matches on Subject: below --
2022-07-18  7:05 Dave Airlie
2022-07-18  7:05 ` Dave Airlie

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=20220718150414.1767bbd8@kernel.org \
    --to=kuba@kernel.org \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=corbet@lwn.net \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.sf.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=mcgrof@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.