Hi,
On 07:05 Tue 21 Jun , Lundberg, Johannes wrote:
> Hi Imre
>
> Thanks for the info! May I ask, isn't your system UEFI, same as mine? Last
> I tried DragonFly didn't support UEFI...
Yes, the HP x2 210 is UEFI only, but DragonFly *can* boot from UEFI :)
I did a port of FreeBSD's UEFI
Hi Imre
Thanks for the info! May I ask, isn't your system UEFI, same as mine? Last
I tried DragonFly didn't support UEFI...
I also had hangs when probing certain I2C controller (maybe it was the
7th...)
Perhaps using linuxkpi and the linux driver would be a good option for
this. i915 uses I2C
So autodetection via smbus(4) probably shouldn't be used at all for this
kind of I2c/smbus.
On my HP x2 210 Cherryview tablet it even causes the system to hard freeze,
when running the autodetection on the 7th I2C controller.
Imre
___
Hi,
No driver for the DMA controller is needed for using the I2C controllers.
On many devices the I2C controllers are only mapped as ACPI devices, and
not as PCI-devices, but the existing ichiic driver can trivially be
adapted to attach via acpi, which is already done by DragonFly's ichiic:
Hi Ian
Thanks for the info. I'll give it a try and see if I have more success.
I'm still uncertain about the role of the DMA controller though. If data
has to be relayed through it or if using it is optional..
Maybe some further testing will reveal the truth..
On Sunday, June 19, 2016, Ian
On Sun, 2016-06-19 at 11:36 -0700, Lundberg, Johannes wrote:
> Hi
>
> I am trying to figure out how to get I2C support on Intel Atom x5
> (Cherryview), which should be same for Baytrail platforms.
>
> On the Serial I/O device (PCI device 24) there are 8 devices.
> #0 is DMA controller
> #1-7 are
Hi
I am trying to figure out how to get I2C support on Intel Atom x5
(Cherryview), which should be same for Baytrail platforms.
On the Serial I/O device (PCI device 24) there are 8 devices.
#0 is DMA controller
#1-7 are I2C controllers (1 & 2 available on GPIO pins).
I assume that all traffic
