u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: "Pali Rohár" <pali@kernel.org>
Cc: Stefan Roese <sr@denx.de>, Bin Meng <bmeng.cn@gmail.com>,
	 Simon Glass <sjg@chromium.org>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v2] pci: Do not enable PCIe GEN3 link retrain workaround by default
Date: Tue, 30 Aug 2022 10:04:51 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2208300928400.61470@angie.orcam.me.uk> (raw)
In-Reply-To: <20220827123005.10239-1-pali@kernel.org>

On Sat, 27 Aug 2022, Pali Rohár wrote:

> Moreover this workaround is enabled for all existing hardware and also all
> future PCIe hardware, which opens a hole that other PCIe vendors may
> introduce same HW issue as on systems where this workaround is required and
> nobody would notice it because U-Boot automatically apply workaround for it.

 Why is it a problem?  Is the intent to cause hassle to end users and 
force them to take action when they have a non-working piece of hardware?  

 I'd say in 99% of cases this will only cause frustration and they won't 
bother.  They will just conclude that either piece of hardware involved is 
broken and will throw it away.  Just as I almost did.  The seller has 
offered me a refund, which seems thought to be a universal solution 
nowadays (but I need to do what I meant to and getting money back doesn't 
solve it).

 And at least I know what U-boot (or indeed firmware) is and have a 
general understanding of how computers work.  Most people just want to 
plug stuff in and use it for whatever their need is.  Expecting them to 
take action to get things working is wasting their time (which BTW seems 
to have been a growing trend in last ~30 years: putting burden on the end 
user to get our problems solved, which saves our time and money at the 
expense of end user's).

 NB I'm slowly getting fed up with the amount of non-working stuff piling 
up around.  Every other piece of equipment I try doesn't work for one 
reason or another and I need to either chase bugs myself or to spend days 
and weeks to persuade someone at least to believe a problem is there to 
get that sorted.  All in my free time I'd rather spend on something else.  
I'd welcome things working automagically for a change so that I could 
focus on what I mean to be doing, and therefore I take breaking things 
deliberately as a major offence.

 FWIW,

  Maciej

  parent reply	other threads:[~2022-08-30  9:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 15:09 [PATCH] pci: Do not enable PCIe ASMedia ASM2824 workaround by default Pali Rohár
2022-04-07  6:33 ` Stefan Roese
2022-04-07 23:18   ` Maciej W. Rozycki
2022-05-01 15:18     ` Pali Rohár
2022-05-05 11:46       ` Maciej W. Rozycki
2022-05-14 13:20         ` Maciej W. Rozycki
2022-08-27 12:30 ` [PATCH v2] pci: Do not enable PCIe GEN3 link retrain " Pali Rohár
2022-08-30  2:30   ` Simon Glass
2022-08-30  9:04   ` Maciej W. Rozycki [this message]
2022-08-30  9:19     ` Pali Rohár
2022-08-30 11:15       ` Stefan Roese
2022-08-30 11:56         ` Pali Rohár
2022-09-17 13:03           ` Maciej W. Rozycki
2022-09-17 13:02         ` Maciej W. Rozycki
2022-09-17 13:02       ` Maciej W. Rozycki

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=alpine.DEB.2.21.2208300928400.61470@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=bmeng.cn@gmail.com \
    --cc=pali@kernel.org \
    --cc=sjg@chromium.org \
    --cc=sr@denx.de \
    --cc=u-boot@lists.denx.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;
as well as URLs for NNTP newsgroup(s).