From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from helium.openadk.org (helium.openadk.org [89.238.66.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0E6552F2905 for ; Wed, 4 Feb 2026 11:19:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=89.238.66.15 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770203962; cv=none; b=gIhnhxDc3rDQByDfL5LJwCj64XDDOBNwXQNzRUoyIFdX8idUb04dJmnOpacJ+puB26maLYH646qyRE04Wo6OBDFnEX2PrGngzAKkesL2h1Co3C5AKpEL5GbgglW/j2wh0fdGErWVrrJggALKn478MBy6VUYFSjUoSxiPt9Bj8DM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770203962; c=relaxed/simple; bh=ZP33gNfyibZuDnGngJwaJ2t7547tAzKfzTo5POg3W4Y=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Mpf+fDMEwDsrKuCBIMvKWhQW+j/tZcc+xfatwvV1Hqb9gg72Idr0dys1NRuKC9TGowULx1DSvoeI8Gq5GOXpcxm3rTF6AUzwJbClSoPH+FBBwXgyeKxRw/HFpr0RB7AMBH9W2t3IMVOvMc6oEHXG/NNbnBCb5vgfl0a6/KNrqAo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=openadk.org; spf=pass smtp.mailfrom=openadk.org; dkim=fail (0-bit key) header.d=openadk.org header.i=@openadk.org header.b=flHUpu0I reason="key not found in DNS"; arc=none smtp.client-ip=89.238.66.15 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=openadk.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=openadk.org Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=openadk.org header.i=@openadk.org header.b="flHUpu0I" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=openadk.org; s=2022; t=1770203959; bh=ZP33gNfyibZuDnGngJwaJ2t7547tAzKfzTo5POg3W4Y=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=flHUpu0I99jozykLnqcM3+f7LXClogbvUxsACMHB7DOtj2ILzoVSoxvHsTNcifgc3 4HSdhdm568hQTh9inpIZTj/sOp+KYGAaMtnyEwHfDzNSDSAIPUHCq5lzmb25Un4twP 5NbLK65F82cJQzosZilldH9vZ/FuAvTifkAGkOy6lxRNbZLlMRJT7JKA2ji9zXtWbG ji3CtM0MM4X6aVMaa1CpmHrfzXB2HKpQEMUknnq/4CgZUUACg6j0kj59IZwlYbI7PJ 6tO0GMtuW3zJKAIL6zhn0W67R98B7O01CDt55bwRNfSToaSCpHYRTCELTjbRZZkptH Om39XHtmOJGeQ== Received: by helium.openadk.org (Postfix, from userid 1000) id D7F4931E0B83; Wed, 04 Feb 2026 12:19:19 +0100 (CET) Date: Wed, 4 Feb 2026 12:19:19 +0100 From: Waldemar Brodkorb To: Jonas Gorski Cc: Waldemar Brodkorb , Jiaxun Yang , "linux-mips@vger.kernel.org" Subject: Re: serial console on Mikrotik RB532 non-working Message-ID: References: <1e9086c1-0cec-4aa7-aab6-e1e605dd9ebf@app.fastmail.com> Precedence: bulk X-Mailing-List: linux-mips@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: Linux 6.12.63+deb13-amd64 x86_64 Hi Jonas, Jonas Gorski wrote, > Hi, > > On Tue, Feb 3, 2026 at 7:25 PM Waldemar Brodkorb wrote: > > > > Hi Jiaxun, > > Jiaxun Yang wrote, > > > > > > On Tue, 3 Feb 2026, at 3:24 PM, Jiaxun Yang wrote: > > > > On Sun, 1 Feb 2026, at 6:39 PM, Waldemar Brodkorb wrote: > > > >> Hi MIPS hackers, > > > >> > > > >> I want to use the latest Linux kernel on my Mikrotik RB532, but the > > > >> serial console is non working. I bisected the problem and the first > > > >> breaking change is this commit: > > > > > > > > Hi, > > > > > > > > Can you try this? > > > > > > Oops sorry I missed a flag, it should be: > > > > > > diff --git a/arch/mips/rb532/devices.c b/arch/mips/rb532/devices.c > > > index 8ecb56be81ac..239018540221 100644 > > > --- a/arch/mips/rb532/devices.c > > > +++ b/arch/mips/rb532/devices.c > > > @@ -213,11 +213,12 @@ static struct platform_device rb532_wdt = { > > > static struct plat_serial8250_port rb532_uart_res[] = { > > > { > > > .type = PORT_16550A, > > > - .membase = (char *)KSEG1ADDR(REGBASE + UART0BASE), > > > + .mapbase = REGBASE + UART0BASE, > > > + .mapsize = SZ_4K, > > > .irq = UART0_IRQ, > > > .regshift = 2, > > > .iotype = UPIO_MEM, > > > - .flags = UPF_BOOT_AUTOCONF, > > > + .flags = UPF_BOOT_AUTOCONF | UPF_IOREMAP, > > > }, > > > { > > > .flags = 0, > > > > > > > I tried the patch, but it still hangs here: > > > > RouterBOOT booter 2.18 > > > > RouterBoard 532 > > > > CPU frequency: 399 MHz > > Memory size: 32 MB > > > > Press any key within 3 seconds to enter setup... > > trying dhcp protocol... OK > > resolved mac address 9C:BF:0D:00:D6:4E > > Gateway: 192.168.1.254 > > transfer started ........................................ transfer ok, time=525.70s > > setting up elf image... OK > > jumping to kernel code > > > > Nothing in tcpdump tries to mount nfs, so I believe serial console > > breakage is not the only problem here. > > Have you tried the patch on top of master or > 6e690d54cfa802f939cefbd2fa2c91bd0b8bd1b6? > > If it works on top of 6e690d54cfa802f939cefbd2fa2c91bd0b8bd1b6, then > it fixes the serial issue, and you can do a new git bisect between > 6e690d54cfa802f939cefbd2fa2c91bd0b8bd1b6 and master to find the next > breakage, with the patch re-applied on top each step (so serial stays > working). Yes, thanks for the idea. I already had this idea in mind and I am 9 steps before I get the next breakage :) Thanks for the heads up, best regards Waldemar