Re: [request for testing] isl, cyapa on chromebooks

2016-10-09 Thread Warner Losh 
On Sun, Oct 9, 2016 at 12:54 AM, Matthias Apitz  wrote:
> El día Sunday, October 09, 2016 a las 01:53:24AM +0200, Michael Gmelin 
> escribió:
>
>> Would I maybe make sense to have man pages for specific laptops (instead
>> of the "FreeBSD Laptop" page, blogs on the internet and Wiki pages).
>>
>> Just thinking that after this change, people will need to know the
>> correct addresses for device.hints to make isl and cyapa work, and
>> putting things like that (and other hints, e.g. to route the Intel HDA
>> correctly) into a man page ("apropos c720") would be the next best
>> thing to having it work out of the box.
>
> Good idea. The problem with such an approach is, that new laptops get
> only inserted into man pages when some maintainer/approver does so and
> seldom if someone brings a new device to working (more or less) with
> FreeBSD.
>
> In the past (some 15 years ago) there was a database and a web frotnend
> where people (everyone) could insert/update a new working device. It was
> here: http://laptop.bsdgroup.de/freebsd/ but the site is offline for
> many year. I even tried and contacted the provide of 'bsdgroup.de' to
> get a copy of the database, w/o any luck.

There seems to be enough information present in the smbios data to
know what devices are at what addresses. Perhaps we should use it as
much as possible in well controlled situations to move this knowledge
into the OS.

Now, where did I put the power supply to my chromebook...

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

vtterm_cngrab is broken on kms-enabled systems when entering kdb

2016-10-09 Thread Andriy Gapon 

JFYI,

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213334

-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [request for testing] isl, cyapa on chromebooks

2016-10-09 Thread Matthias Apitz 


Thanks. Changing device.hints to

iicbus14
iicbus15

makes cyapa(4) attaching and moused working fine. I will later install xorg 
into this memstick.


matthias




--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [request for testing] isl, cyapa on chromebooks

2016-10-09 Thread Matthias Apitz 
El día Sunday, October 09, 2016 a las 01:53:24AM +0200, Michael Gmelin escribió:

> Would I maybe make sense to have man pages for specific laptops (instead
> of the "FreeBSD Laptop" page, blogs on the internet and Wiki pages).
> 
> Just thinking that after this change, people will need to know the
> correct addresses for device.hints to make isl and cyapa work, and
> putting things like that (and other hints, e.g. to route the Intel HDA
> correctly) into a man page ("apropos c720") would be the next best
> thing to having it work out of the box.

Good idea. The problem with such an approach is, that new laptops get
only inserted into man pages when some maintainer/approver does so and
seldom if someone brings a new device to working (more or less) with
FreeBSD.

In the past (some 15 years ago) there was a database and a web frotnend
where people (everyone) could insert/update a new working device. It was
here: http://laptop.bsdgroup.de/freebsd/ but the site is offline for
many year. I even tried and contacted the provide of 'bsdgroup.de' to
get a copy of the database, w/o any luck.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Einheitsfeier? Nein, danke! Kann ich bitte mein Land wiederhaben und am 7. 
Oktober feiern.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [request for testing] isl, cyapa on chromebooks

2016-10-09 Thread Andriy Gapon 
On 09/10/2016 09:36, Matthias Apitz wrote:
> El día Saturday, October 08, 2016 a las 10:17:07PM +0300, Andriy Gapon 
> escribió:
> 
>> On 08/10/2016 21:07, Matthias Apitz wrote:
>>> I have now produced a memstick with (unpatched) r306769 of October 6. It 
>>> boots
>>> fine in my Acer C720 Chromebook and the moused is working fine with the
>>> cyapa(4) driver. I will apply tomorrow the above v4 patch or is there
>>> anything newer? And will test/report.
>>
>> v4 is the latest.  Thanks!
> 
> The patch applies cleanly, the 'make buildkernel' does fine and system
> boots, but cyapa(4) can not bring the device out of bootstrap. The verbose 
> dmesg
> is here http://www.unixarea.de/dmesg-00.txt 
> 
> And yes, I have in /boot/device.hints:

Well, comparing the hints and the boot message, you have exactly the problem
that I feared many people would have until we add auto-probing to isl and cyapa.

Basically it's easy to connect the dots once you know what they are.  You hint
that isl and cyapa should be on iicbus0 or iicbus1.  But iicbus0 is connected to
iicbb0 which is intel_iicbb0 on drmn0, which is a video card.  That is clearly
wrong.  And a similar thing with iicbus1:  on intel_gmbus0.
But later you have:
iicbus14:  on ig4iic0
iicbus15:  on ig4iic1
So, in your case, and with that probing order (hopefully it not changes from
boot to boot), you should use those two buses to look for isl and cyapa.

Examining output of devinfo -v -r should be even easier than going through 
dmesg.
Hope this helps.

> ...
> # The change moves the drivers from the SMBus to the I2C bus and as such some
> # configuration changes are required.
> # Namely, you will now need iicbus driver either in the kernel configuration 
> or as
> # a module.  For now the smbus driver is also required.
> # You also need to add some entries to /boot/device.hints:
> # 
> hint.isl.0.at="iicbus0"
> hint.isl.0.addr=0x88
> hint.isl.1.at="iicbus1"
> hint.isl.1.addr=0x88
> hint.cyapa.0.at="iicbus0"
> hint.cyapa.0.addr=0xce
> hint.cyapa.1.at="iicbus1"
> hint.cyapa.1.addr=0xce
> # 
> # The hints are required because auto-probing (either via the bus enumeration 
> or
> # self-identification) is disabled for now for safety reason.
> # Also, as I understand, the Intel chipset used in the supported Chromebooks
> # provides to i2c buses (possibly in addition in an smbus) and I am not sure 
> on
> # which of the i2c buses the devices reside.
> 
> Please let me know what to check/debug.
> 
>   matthias
> 


-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [request for testing] isl, cyapa on chromebooks

2016-10-09 Thread Matthias Apitz 
El día Saturday, October 08, 2016 a las 10:17:07PM +0300, Andriy Gapon escribió:

> On 08/10/2016 21:07, Matthias Apitz wrote:
> > I have now produced a memstick with (unpatched) r306769 of October 6. It 
> > boots
> > fine in my Acer C720 Chromebook and the moused is working fine with the
> > cyapa(4) driver. I will apply tomorrow the above v4 patch or is there
> > anything newer? And will test/report.
> 
> v4 is the latest.  Thanks!

The patch applies cleanly, the 'make buildkernel' does fine and system
boots, but cyapa(4) can not bring the device out of bootstrap. The verbose dmesg
is here http://www.unixarea.de/dmesg-00.txt 

And yes, I have in /boot/device.hints:

...
# The change moves the drivers from the SMBus to the I2C bus and as such some
# configuration changes are required.
# Namely, you will now need iicbus driver either in the kernel configuration or 
as
# a module.  For now the smbus driver is also required.
# You also need to add some entries to /boot/device.hints:
# 
hint.isl.0.at="iicbus0"
hint.isl.0.addr=0x88
hint.isl.1.at="iicbus1"
hint.isl.1.addr=0x88
hint.cyapa.0.at="iicbus0"
hint.cyapa.0.addr=0xce
hint.cyapa.1.at="iicbus1"
hint.cyapa.1.addr=0xce
# 
# The hints are required because auto-probing (either via the bus enumeration or
# self-identification) is disabled for now for safety reason.
# Also, as I understand, the Intel chipset used in the supported Chromebooks
# provides to i2c buses (possibly in addition in an smbus) and I am not sure on
# which of the i2c buses the devices reside.

Please let me know what to check/debug.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Einheitsfeier? Nein, danke! Kann ich bitte mein Land wiederhaben und am 7. 
Oktober feiern.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"