mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Imre Kaloz <kaloz@kernel.org>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] MIPS: SGI-IP30: fix the defconfig defaults for the Bridge PROM and RTC
Date: Thu, 5 Nov 2026 16:22:21 +0100	[thread overview]
Message-ID: <auyfLWftx35e-Bk2@alpha.franken.de> (raw)
In-Reply-To: <20261013094554.16804-4-kaloz@kernel.org>

On Tue, Oct 13, 2026 at 11:45:54AM +0200, Imre Kaloz wrote:
> The Bridge probe reads its part number from the 1-wire PROM and defers
> until the SGI 1-wire master and DS250x slave are present, so without
> them there is no PCI bus and no serial console.
> 
> The IP30 RTC is a DS1685-family part, but the defconfig, derived from
> ip27_defconfig, has the M48T35 driver, so there is no RTC.
> 
> Enable the 1-wire drivers and select the DS1685 family.
> 
> Also drop four lines that savedefconfig removes, as CRYPTO_CAMELLIA,
> CRYPTO_CTS and CRYPTO_HMAC are selected built-in and IPV6_SIT=m is the
> default.
> 
> Fixes: bb2d63500b5c ("MIPS: config: Add ip30_defconfig")
> Signed-off-by: Imre Kaloz <kaloz@kernel.org>
> ---
>  arch/mips/configs/ip30_defconfig | 9 ++++-----
>  1 file changed, 4 insertions(+), 5 deletions(-)

applied to mips-fixes

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2026-11-05 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  9:45 [PATCH 0/3] MIPS: SGI fixes Imre Kaloz
2026-10-13  9:45 ` [PATCH 1/3] MIPS: sgi-ip32: Clear latched CRIME errors at boot Imre Kaloz
2026-10-13  9:45 ` [PATCH 2/3] MIPS: sgi-ip32: Reserve the firmware memory Imre Kaloz
2026-10-13  9:45 ` [PATCH 3/3] MIPS: SGI-IP30: fix the defconfig defaults for the Bridge PROM and RTC Imre Kaloz
2026-11-05 15:22   ` Thomas Bogendoerfer [this message]

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=auyfLWftx35e-Bk2@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=kaloz@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®