On Sat, Feb 03, 2018 at 12:47:48PM +1100, Jonathan Gray wrote:
> On Sun, Jan 28, 2018 at 01:54:25PM -0500, Tom Rini wrote:
> > On Tue, Jan 23, 2018 at 06:05:21PM +0100, Alexander Graf wrote:
> >
> > > The bcm283x family of SoCs have a GPIO controller that also acts as
> > > pinctrl controller.
> >
On 02/09/2018 05:41 AM, Heinrich Schuchardt wrote:
> On 02/09/2018 05:12 AM, Jonathan Gray wrote:
>> On Fri, Feb 09, 2018 at 04:43:09AM +0100, Heinrich Schuchardt wrote:
>>> On 02/09/2018 12:55 AM, Jonathan Gray wrote:
On Thu, Feb 08, 2018 at 03:44:32PM +0100, Heinrich Schuchardt wrote:
>
On 02/09/2018 05:12 AM, Jonathan Gray wrote:
On Fri, Feb 09, 2018 at 04:43:09AM +0100, Heinrich Schuchardt wrote:
On 02/09/2018 12:55 AM, Jonathan Gray wrote:
On Thu, Feb 08, 2018 at 03:44:32PM +0100, Heinrich Schuchardt wrote:
On 02/08/2018 10:49 AM, Jonathan Gray wrote:
On Thu, Feb 08, 2018
On Fri, Feb 09, 2018 at 04:43:09AM +0100, Heinrich Schuchardt wrote:
> On 02/09/2018 12:55 AM, Jonathan Gray wrote:
> > On Thu, Feb 08, 2018 at 03:44:32PM +0100, Heinrich Schuchardt wrote:
> > > On 02/08/2018 10:49 AM, Jonathan Gray wrote:
> > > > On Thu, Feb 08, 2018 at 08:10:47PM +1100, Jonathan
On 02/09/2018 12:55 AM, Jonathan Gray wrote:
On Thu, Feb 08, 2018 at 03:44:32PM +0100, Heinrich Schuchardt wrote:
On 02/08/2018 10:49 AM, Jonathan Gray wrote:
On Thu, Feb 08, 2018 at 08:10:47PM +1100, Jonathan Gray wrote:
On Thu, Feb 08, 2018 at 09:11:20AM +0100, Alexander Graf wrote:
Am 0
On Thu, Feb 08, 2018 at 03:44:32PM +0100, Heinrich Schuchardt wrote:
> On 02/08/2018 10:49 AM, Jonathan Gray wrote:
> > On Thu, Feb 08, 2018 at 08:10:47PM +1100, Jonathan Gray wrote:
> >> On Thu, Feb 08, 2018 at 09:11:20AM +0100, Alexander Graf wrote:
> >>>
> >>>
> Am 08.02.2018 um 06:49 schri
On 02/08/2018 10:49 AM, Jonathan Gray wrote:
> On Thu, Feb 08, 2018 at 08:10:47PM +1100, Jonathan Gray wrote:
>> On Thu, Feb 08, 2018 at 09:11:20AM +0100, Alexander Graf wrote:
>>>
>>>
Am 08.02.2018 um 06:49 schrieb Jonathan Gray :
On Mon, Feb 05, 2018 at 11:31:42AM +0100, Mark Kette
On Thu, Feb 08, 2018 at 08:10:47PM +1100, Jonathan Gray wrote:
> On Thu, Feb 08, 2018 at 09:11:20AM +0100, Alexander Graf wrote:
> >
> >
> > > Am 08.02.2018 um 06:49 schrieb Jonathan Gray :
> > >
> > > On Mon, Feb 05, 2018 at 11:31:42AM +0100, Mark Kettenis wrote:
> > >>> Date: Mon, 5 Feb 2018 2
On Thu, Feb 08, 2018 at 09:11:20AM +0100, Alexander Graf wrote:
>
>
> > Am 08.02.2018 um 06:49 schrieb Jonathan Gray :
> >
> > On Mon, Feb 05, 2018 at 11:31:42AM +0100, Mark Kettenis wrote:
> >>> Date: Mon, 5 Feb 2018 21:06:59 +1100
> >>> From: Jonathan Gray
> >>>
> > booting sd0a:/bsd: op
> Am 08.02.2018 um 06:49 schrieb Jonathan Gray :
>
> On Mon, Feb 05, 2018 at 11:31:42AM +0100, Mark Kettenis wrote:
>>> Date: Mon, 5 Feb 2018 21:06:59 +1100
>>> From: Jonathan Gray
>>>
> booting sd0a:/bsd: open sd0a:/bsd: Device not configured
> failed(6). will try /bsd
How
On Mon, Feb 05, 2018 at 11:31:42AM +0100, Mark Kettenis wrote:
> > Date: Mon, 5 Feb 2018 21:06:59 +1100
> > From: Jonathan Gray
> >
> > > > booting sd0a:/bsd: open sd0a:/bsd: Device not configured
> > > > failed(6). will try /bsd
> > >
> > > How do you find out that it's sd0a instead of sd1a?
>
> Date: Mon, 5 Feb 2018 21:06:59 +1100
> From: Jonathan Gray
>
> > > booting sd0a:/bsd: open sd0a:/bsd: Device not configured
> > > failed(6). will try /bsd
> >
> > How do you find out that it's sd0a instead of sd1a?
>
> The loaded image protocol I believe.
Actually the OpenBSD bootloader cur
On Mon, Feb 05, 2018 at 09:37:15AM +0100, Alexander Graf wrote:
>
>
> On 03.02.18 12:38, Jonathan Gray wrote:
> > On Sat, Feb 03, 2018 at 09:02:25AM +0100, Alexander Graf wrote:
> >>
> >>
> >> On 03.02.18 02:47, Jonathan Gray wrote:
> >>> On Sun, Jan 28, 2018 at 01:54:25PM -0500, Tom Rini wrote:
On 03.02.18 12:38, Jonathan Gray wrote:
> On Sat, Feb 03, 2018 at 09:02:25AM +0100, Alexander Graf wrote:
>>
>>
>> On 03.02.18 02:47, Jonathan Gray wrote:
>>> On Sun, Jan 28, 2018 at 01:54:25PM -0500, Tom Rini wrote:
On Tue, Jan 23, 2018 at 06:05:21PM +0100, Alexander Graf wrote:
>
On Sat, Feb 03, 2018 at 09:02:25AM +0100, Alexander Graf wrote:
>
>
> On 03.02.18 02:47, Jonathan Gray wrote:
> > On Sun, Jan 28, 2018 at 01:54:25PM -0500, Tom Rini wrote:
> >> On Tue, Jan 23, 2018 at 06:05:21PM +0100, Alexander Graf wrote:
> >>
> >>> The bcm283x family of SoCs have a GPIO contro
On 03.02.18 02:47, Jonathan Gray wrote:
> On Sun, Jan 28, 2018 at 01:54:25PM -0500, Tom Rini wrote:
>> On Tue, Jan 23, 2018 at 06:05:21PM +0100, Alexander Graf wrote:
>>
>>> The bcm283x family of SoCs have a GPIO controller that also acts as
>>> pinctrl controller.
>>>
>>> This patch introduces a
On Sun, Jan 28, 2018 at 01:54:25PM -0500, Tom Rini wrote:
> On Tue, Jan 23, 2018 at 06:05:21PM +0100, Alexander Graf wrote:
>
> > The bcm283x family of SoCs have a GPIO controller that also acts as
> > pinctrl controller.
> >
> > This patch introduces a new pinctrl driver that can actually proper
On Tue, Jan 23, 2018 at 06:05:21PM +0100, Alexander Graf wrote:
> The bcm283x family of SoCs have a GPIO controller that also acts as
> pinctrl controller.
>
> This patch introduces a new pinctrl driver that can actually properly mux
> devices into their device tree defined pin states and is now
18 matches
Mail list logo