mbox series

[0/2] MIPS: SiByte: Update SWARM defconfig for PATA support

Message ID alpine.DEB.2.21.2103212028360.21463@angie.orcam.me.uk (mailing list archive)
Headers show
Series MIPS: SiByte: Update SWARM defconfig for PATA support | expand

Message

Maciej W. Rozycki March 21, 2021, 7:55 p.m. UTC
Hi,

 In the course of looking into Christoph's recent proposal to drop legacy 
IDE drivers I have noticed that SiByte SWARM's defconfig does not enable 
the pata_platform driver for the onboard PATA interface.  I think default 
configuration ought to enable all the supported onboard devices unless 
there are specific reasons so as not to, and the PATA interface is one of 
the boot devices supported by the CFE firmware, so I think even more then 
that it should be included by default.

 Change split into two because the defconfig has become stale since the 
last update, so 1/2 first regenerates it, and then 2/2 applies the actual 
modification.

 Sadly I'm currently away from my SWARM board for the foreseeable future 
and I have no remote access to it either, but this is supposed not to need 
run-time verification.  Build-tested only then.

 Please apply.

  Maciej

Comments

Thomas Bogendoerfer March 24, 2021, 10:02 a.m. UTC | #1
On Sun, Mar 21, 2021 at 08:55:37PM +0100, Maciej W. Rozycki wrote:
> Hi,
> 
>  In the course of looking into Christoph's recent proposal to drop legacy 
> IDE drivers I have noticed that SiByte SWARM's defconfig does not enable 
> the pata_platform driver for the onboard PATA interface.  I think default 
> configuration ought to enable all the supported onboard devices unless 
> there are specific reasons so as not to, and the PATA interface is one of 
> the boot devices supported by the CFE firmware, so I think even more then 
> that it should be included by default.
> 
>  Change split into two because the defconfig has become stale since the 
> last update, so 1/2 first regenerates it, and then 2/2 applies the actual 
> modification.
> 
>  Sadly I'm currently away from my SWARM board for the foreseeable future 
> and I have no remote access to it either, but this is supposed not to need 
> run-time verification.  Build-tested only then.
> 
>  Please apply.

series applied to mips-next.

Thomas.