On Fri, Aug 26, 2016 at 02:20:50PM -0400, Alan Stern wrote:
> On Fri, 26 Aug 2016, Russell King - ARM Linux wrote:
>
> > On Fri, Aug 26, 2016 at 01:18:25PM -0400, Alan Stern wrote:
> > > On Fri, 26 Aug 2016, Russell King wrote:
> > >
> > > > The neponset is a daughter board for the Assabet platfo
On Fri, 26 Aug 2016, Russell King - ARM Linux wrote:
> On Fri, Aug 26, 2016 at 01:18:25PM -0400, Alan Stern wrote:
> > On Fri, 26 Aug 2016, Russell King wrote:
> >
> > > The neponset is a daughter board for the Assabet platform, which has a
> > > SA chip on it. If we're initialising the SA11
On Fri, Aug 26, 2016 at 01:18:25PM -0400, Alan Stern wrote:
> On Fri, 26 Aug 2016, Russell King wrote:
>
> > The neponset is a daughter board for the Assabet platform, which has a
> > SA chip on it. If we're initialising the SA OHCI, and we're
> > part of a neponset, the host platform mus
On Fri, 26 Aug 2016, Russell King wrote:
> The neponset is a daughter board for the Assabet platform, which has a
> SA chip on it. If we're initialising the SA OHCI, and we're
> part of a neponset, the host platform must be an Assabet.
>
> This allows us to eliminate machine_has_neponset
The neponset is a daughter board for the Assabet platform, which has a
SA chip on it. If we're initialising the SA OHCI, and we're
part of a neponset, the host platform must be an Assabet.
This allows us to eliminate machine_has_neponset() from this driver,
replacing it instead with machi
