On Tue, 2018-04-10 at 15:06 +0200, Arnd Bergmann wrote:
> On Tue, Apr 10, 2018 at 2:57 PM, Benjamin Herrenschmidt
> wrote:
> > On Tue, 2018-04-10 at 13:29 +0200, Arnd Bergmann wrote:
> > > In the cases where an ad-hoc interface is needed, I can see
> > > two options: we can stick something in driv
On Tue, Apr 10, 2018 at 2:57 PM, Benjamin Herrenschmidt
wrote:
> On Tue, 2018-04-10 at 13:29 +0200, Arnd Bergmann wrote:
>> In the cases where an ad-hoc interface is needed, I can see
>> two options: we can stick something in drivers/soc that exposes
>> it in the least ugly way, completely specif
On Tue, 2018-04-10 at 13:29 +0200, Arnd Bergmann wrote:
> > Any better idea ? It's a fairly simple problem, and the above solution
> > would be very little code, but I just don't want us to go down a rabbit
> > hole if some of you have religious objections to some of it :)
>
> I think the hard pa
On Tue, Apr 10, 2018 at 11:17 AM, Benjamin Herrenschmidt
wrote:
> Hi Folks !
>
> I would like to discuss something we need to solve for BMC chips before
> we start implementing a solution that you'll reject upstream :-)
>
> So quick recap: the BMC chip is the management controller of your
> server
Hi Folks !
I would like to discuss something we need to solve for BMC chips before
we start implementing a solution that you'll reject upstream :-)
So quick recap: the BMC chip is the management controller of your
server, typically some kind of specialized ARM SoC which controls a
variety of thin
5 matches
Mail list logo
