From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754573AbdKAMJS (ORCPT ); Wed, 1 Nov 2017 08:09:18 -0400 Received: from mail-wr0-f196.google.com ([209.85.128.196]:48585 "EHLO mail-wr0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751738AbdKAMJQ (ORCPT ); Wed, 1 Nov 2017 08:09:16 -0400 X-Google-Smtp-Source: ABhQp+Q4GS/uy4wqqqt4QnG//prlr0m4RrZ/6dxMnYvhlCc2JjivyOs+mbaQjYG9aNydVLzOT5qTwZxWlp9vVM2YFUI= MIME-Version: 1.0 In-Reply-To: <910a98ca-57f6-baca-73ac-f6c8c1ff04db@i2se.com> References: <20171006220504.7776-1-eric@anholt.net> <910a98ca-57f6-baca-73ac-f6c8c1ff04db@i2se.com> From: Peter Robinson Date: Wed, 1 Nov 2017 12:09:14 +0000 Message-ID: Subject: Re: [GIT PULL 1/2] bcm2835-dt-fixes-2017-10-06 To: Stefan Wahren Cc: Matt Hart , Marcel Holtmann , linux-kernel@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, Loic Poulain , linux-arm-kernel@lists.infradead.org, Eric Anholt Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 1, 2017 at 12:05 PM, Stefan Wahren wrote: > Hi Matt, hi Peter, > > Am 01.11.2017 um 10:37 schrieb Peter Robinson: >> On Tue, Oct 31, 2017 at 5:00 PM, Matt Hart wrote: >>> On 6 October 2017 at 23:14, Florian Fainelli wrote: >>>> On 10/06/2017 03:05 PM, Eric Anholt wrote: >>>>> Hi Florian. Here's a patch that's gone through a couple of revisions >>>>> on the list, that seriously fixes up the default serial behavior -- >>>>> previously, without the right config.txt/cmdline bits, you'd often end >>>>> up with a hang with no output before booting completed. It would be >>>>> great to get it into 4.14. >>>>> >>>>> The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: >>>>> >>>>> Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) >>>>> >>>>> are available in the git repository at: >>>>> >>>>> git://github.com/anholt/linux tags/bcm2835-dt-fixes-2017-10-06 >>>>> >>>>> for you to fetch changes up to f08f58a2bf68900a84e782b8c7ad701c0654173c: >>>>> >>>>> ARM: dts: bcm283x: Fix console path on RPi3 (2017-10-06 13:04:56 -0700) >>>>> >>>>> ---------------------------------------------------------------- >>>>> This pull request brings in a fix for default serial console setup on >>>>> RPi3, so it now comes up with no config.txt/cmdline.txt settings in >>>>> the firmware. >>>>> >>>>> ---------------------------------------------------------------- >>>> Merged, thanks Eric >>>> >>>> -- >>>> Florian >>> Hi all, >>> >>> I realise this patch has been in mainline for a more than a week, but >>> I've only recently had time to bisect broken rpi-3 boots in kernelci >>> and found f08f58a2bf68900a84e782b8c7ad701c0654173c as the cause. >>> >>> Kernelci boots the rpi3 using uboot, with console=ttyS0 in the command >>> line which now fails: >>> https://kernelci.org/boot/id/59f787f059b5147794ef1dcf/ >>> >>> Is there an alias I can use for both before and after this patch? >>> >>> Mainline boots fine if I use console=ttyS1 or drop the console arg >>> altogether, but as we don't currently support different boot args per >>> tree, and we don't have the manpower to track this patch in all the >>> trees we test, we will have to switch to only boot testing mainline >>> from now on. >> Yes, I've seen the same in Fedora with that patch. >> >> > could you please describe the issue more in detail. > > Does u-boot or Linux hang? Does u-boot select the wrong UART? Is there a > pinmux conflict? Basically on the RPi3 you use to get ttyAMA0 and ttyS0 but now the later is ttyS1 > Which u-boot version do you use? Upstream From mboxrd@z Thu Jan 1 00:00:00 1970 From: pbrobinson@gmail.com (Peter Robinson) Date: Wed, 1 Nov 2017 12:09:14 +0000 Subject: [GIT PULL 1/2] bcm2835-dt-fixes-2017-10-06 In-Reply-To: <910a98ca-57f6-baca-73ac-f6c8c1ff04db@i2se.com> References: <20171006220504.7776-1-eric@anholt.net> <910a98ca-57f6-baca-73ac-f6c8c1ff04db@i2se.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Nov 1, 2017 at 12:05 PM, Stefan Wahren wrote: > Hi Matt, hi Peter, > > Am 01.11.2017 um 10:37 schrieb Peter Robinson: >> On Tue, Oct 31, 2017 at 5:00 PM, Matt Hart wrote: >>> On 6 October 2017 at 23:14, Florian Fainelli wrote: >>>> On 10/06/2017 03:05 PM, Eric Anholt wrote: >>>>> Hi Florian. Here's a patch that's gone through a couple of revisions >>>>> on the list, that seriously fixes up the default serial behavior -- >>>>> previously, without the right config.txt/cmdline bits, you'd often end >>>>> up with a hang with no output before booting completed. It would be >>>>> great to get it into 4.14. >>>>> >>>>> The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: >>>>> >>>>> Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) >>>>> >>>>> are available in the git repository at: >>>>> >>>>> git://github.com/anholt/linux tags/bcm2835-dt-fixes-2017-10-06 >>>>> >>>>> for you to fetch changes up to f08f58a2bf68900a84e782b8c7ad701c0654173c: >>>>> >>>>> ARM: dts: bcm283x: Fix console path on RPi3 (2017-10-06 13:04:56 -0700) >>>>> >>>>> ---------------------------------------------------------------- >>>>> This pull request brings in a fix for default serial console setup on >>>>> RPi3, so it now comes up with no config.txt/cmdline.txt settings in >>>>> the firmware. >>>>> >>>>> ---------------------------------------------------------------- >>>> Merged, thanks Eric >>>> >>>> -- >>>> Florian >>> Hi all, >>> >>> I realise this patch has been in mainline for a more than a week, but >>> I've only recently had time to bisect broken rpi-3 boots in kernelci >>> and found f08f58a2bf68900a84e782b8c7ad701c0654173c as the cause. >>> >>> Kernelci boots the rpi3 using uboot, with console=ttyS0 in the command >>> line which now fails: >>> https://kernelci.org/boot/id/59f787f059b5147794ef1dcf/ >>> >>> Is there an alias I can use for both before and after this patch? >>> >>> Mainline boots fine if I use console=ttyS1 or drop the console arg >>> altogether, but as we don't currently support different boot args per >>> tree, and we don't have the manpower to track this patch in all the >>> trees we test, we will have to switch to only boot testing mainline >>> from now on. >> Yes, I've seen the same in Fedora with that patch. >> >> > could you please describe the issue more in detail. > > Does u-boot or Linux hang? Does u-boot select the wrong UART? Is there a > pinmux conflict? Basically on the RPi3 you use to get ttyAMA0 and ttyS0 but now the later is ttyS1 > Which u-boot version do you use? Upstream