gpioiic broken

[Mori Hiroki]

Hi

sorry too late reply.

I have no time debug this issue.

I also use gpioiic on RTL8366SR etherswitch controle on Buffalo_WZR-HP-G300NN.

It's also panic in boot.

If you can't debug this then I think revert this change
on 12-STABLE. Because of STABLE to be stable. STABLE is 
NOT CURRENT.

Thanks

Hiroki Mori

----- Original Message -----
>From: Ian Lepore <ian at freebsd.org>
>To: Adrian Chadd <adrian.chadd at gmail.com>; Mori Hiroki <yamori813 at yahoo.co.jp> 
>Cc: "freebsd-mips at freebsd.org" <freebsd-mips at freebsd.org>
>Date: 2020/2/20, Thu 11:18
>Subject: Re: gpioiic broken
> 
>On Wed, 2020-02-19 at 17:55 -0800, Adrian Chadd wrote:
>> On Tue, 18 Feb 2020 at 01:00, Mori Hiroki <yamori813 at yahoo.co.jp>
>> wrote:
>> > 
>> > Hi
>> > 
>> > Now CURRENT is very very very unstable.
>> > 
>> > Please do stable at STABLE.
>> > 
>> 
>> 
>> hm, how's -head unstable for you on mips?
>> 
>> It was fine a month or two ago when i last updated.
>> 
>> re: iic, i can give it a whirl; maybe it's a device ordering thing we
>> need to just express in our hints files for mips?
>> 
>> -a
>
>Even just decoding a bit of this:
>
>--- exception, cause ffffffff80566100 badvaddr ffffffff8014a334 ---
>device_get_nameunit (?,?,?,?) ra 8007521c sp 803b8ba8 sz 0
>gpio_pin_getcaps+0xd08 (?,?,?,?) ra 0 sp 803b8ba8 sz 0
>
>like turning gpio_pin_getcaps+0xd08 into file+line of kernel source
>would be a good clue.
>
>-- Ian
>
>
>
>