On 12/10/2016 09:21, Andriy Gapon wrote:
> On 12/10/2016 07:03, Warner Losh wrote:
>> I think I can do the device table mechanism if Andriy isn't up for it.
>
> That would be great, thank you!
>
Meanwhile, I've added a "stop-gap" version of 'chromebook_platform' driver here:
On 12/10/2016 07:03, Warner Losh wrote:
> I think I can do the device table mechanism if Andriy isn't up for it.
That would be great, thank you!
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
On Mon, Oct 10, 2016 at 12:45 PM, Michael Gmelin wrote:
>
>
>> On 10 Oct 2016, at 20:27, Matthias Apitz wrote:
>>
>>> El día Monday, October 10, 2016 a las 09:26:26AM -0600, Warner Losh
>>> escribió:
>>>
>>> I see no reason not to start the table right away
On 10/10/2016 21:45, Michael Gmelin wrote:
> I see three tasks here: - Andriy finishes his change, moving things from
> smbus to iicbus, adding some workaround to keep the user experience like it
> is - Someone else implements the device table mechanism for auto detection -
> Someone else ports
> On 10 Oct 2016, at 20:27, Matthias Apitz wrote:
>
>> El día Monday, October 10, 2016 a las 09:26:26AM -0600, Warner Losh escribió:
>>
>> I see no reason not to start the table right away based on
>> smbios.sys.product and other criteria. I don't think we need all the
>>
El día Monday, October 10, 2016 a las 09:26:26AM -0600, Warner Losh escribió:
> I see no reason not to start the table right away based on
> smbios.sys.product and other criteria. I don't think we need all the
> matches that Linux uses, but we can expand the table if we find it so.
> Why have a
On 10/10/2016 18:26, Warner Losh wrote:
> I see no reason not to start the table right away based on
> smbios.sys.product and other criteria. I don't think we need all the
> matches that Linux uses, but we can expand the table if we find it so.
> Why have a stop gap that's a table that we kludge
I see no reason not to start the table right away based on
smbios.sys.product and other criteria. I don't think we need all the
matches that Linux uses, but we can expand the table if we find it so.
Why have a stop gap that's a table that we kludge together when the
real table is of comparable
On Mon, 10 Oct 2016 14:35:22 +0300
Andriy Gapon wrote:
> On 09/10/2016 23:22, Warner Losh wrote:
> > 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
On 09/10/2016 23:22, Warner Losh wrote:
> 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.
So, I was thinking about maybe
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
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
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
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
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
> >
On Sat, 8 Oct 2016 15:54:27 -0600
Warner Losh wrote:
> Speaking of Chromebooks, what's the best way to put FreeBSD onto one?
>
> Warner
>
>
Depends on the Chromebook in question, when porting the drivers for the
c720, I wrote a blog post about it (quite a while ago):
On Saturday, 8 October 2016 23:54:27 CEST, Warner Losh
wrote:
Speaking of Chromebooks, what's the best way to put FreeBSD onto one?
Set it to developer mode or Legacy boot, boot and install 11-C or 12-C from
USB.
matthias
--
Sent from my Ubuntu phone
Speaking of Chromebooks, what's the best way to put FreeBSD onto one?
Warner
On Sat, Oct 8, 2016 at 1:17 PM, Andriy Gapon wrote:
> 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
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
El día Thursday, October 06, 2016 a las 11:12:27AM +0300, Andriy Gapon escribió:
> On 06/10/2016 11:10, Michael Gmelin wrote:
> >
> >
> >> On 06 Oct 2016, at 09:48, Andriy Gapon wrote:
> >>
> >>> On 06/10/2016 08:37, Andriy Gapon wrote:
> >>> The more testing the better!
> >>
On Thu, 6 Oct 2016 11:12:27 +0300
Andriy Gapon wrote:
> On 06/10/2016 11:10, Michael Gmelin wrote:
> >
> >
> >> On 06 Oct 2016, at 09:48, Andriy Gapon wrote:
> >>
> >>> On 06/10/2016 08:37, Andriy Gapon wrote:
> >>> The more testing the better!
> >>
>
On 06/10/2016 11:10, Michael Gmelin wrote:
>
>
>> On 06 Oct 2016, at 09:48, Andriy Gapon wrote:
>>
>>> On 06/10/2016 08:37, Andriy Gapon wrote:
>>> The more testing the better!
>>
>> Based on Michael's results I've uploaded a new version:
>>
> On 06 Oct 2016, at 09:48, Andriy Gapon wrote:
>
>> On 06/10/2016 08:37, Andriy Gapon wrote:
>> The more testing the better!
>
> Based on Michael's results I've uploaded a new version:
> https://people.freebsd.org/~avg/ig4-i2c.v4.diff
>
>
Good news. Applying the last two
On 06/10/2016 08:37, Andriy Gapon wrote:
> The more testing the better!
Based on Michael's results I've uploaded a new version:
https://people.freebsd.org/~avg/ig4-i2c.v4.diff
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
On 06/10/2016 10:25, Andriy Gapon wrote:
> On 06/10/2016 10:08, Michael Gmelin wrote:
>>
>>
>>> On 05 Oct 2016, at 15:01, Andriy Gapon wrote:
>>>
On 05/10/2016 14:19, Michael Gmelin wrote:
ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe
On 06/10/2016 10:08, Michael Gmelin wrote:
>
>
>> On 05 Oct 2016, at 15:01, Andriy Gapon wrote:
>>
>>> On 05/10/2016 14:19, Michael Gmelin wrote:
>>>
>>> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and
>>> iicbus_attach are not.
>>
>> Thank you!
>>
> On 05 Oct 2016, at 15:01, Andriy Gapon wrote:
>
>> On 05/10/2016 14:19, Michael Gmelin wrote:
>>
>> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and
>> iicbus_attach are not.
>
> Thank you!
> Now I think I see where I made a silly mistake.
>
On 06/10/2016 07:47, Matthias Apitz wrote:
> El día Wednesday, October 05, 2016 a las 04:01:25PM +0300, Andriy Gapon
> escribió:
>
>> On 05/10/2016 14:19, Michael Gmelin wrote:
>>>
>>> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and
>>> iicbus_attach are not.
>>
>>
El día Wednesday, October 05, 2016 a las 04:01:25PM +0300, Andriy Gapon
escribió:
> On 05/10/2016 14:19, Michael Gmelin wrote:
> >
> > ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and
> > iicbus_attach are not.
>
> Thank you!
> Now I think I see where I made a silly
On 05/10/2016 14:19, Michael Gmelin wrote:
>
> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and
> iicbus_attach are not.
Thank you!
Now I think I see where I made a silly mistake.
Please try an updated version of the patch from here
Nice! I'd love to follow along in development and learn whatever can. I've
never worked at device driver level before. Do you have a suggested time I
can start harassing you more about testing?
Den 5 okt. 2016 13:48 skrev "Michael Gmelin" :
>
>
> On 05 Oct 2016, at 13:32,
Den 5 okt. 2016 13:19 skrev "Michael Gmelin" :
>
>
>
> > On 05 Oct 2016, at 07:48, Andriy Gapon wrote:
> >
> >> On 05/10/2016 01:48, Michael Gmelin wrote:
> >> Double-checked the hints, it's all ok.
> >>
> >> Please find a more verbose log file of loading the
> On 05 Oct 2016, at 13:32, Malcolm Matalka wrote:
>
> Den 5 okt. 2016 13:19 skrev "Michael Gmelin" :
> >
> >
> >
> > > On 05 Oct 2016, at 07:48, Andriy Gapon wrote:
> > >
> > >> On 05/10/2016 01:48, Michael Gmelin wrote:
> > >>
> On 05 Oct 2016, at 07:48, Andriy Gapon wrote:
>
>> On 05/10/2016 01:48, Michael Gmelin wrote:
>> Double-checked the hints, it's all ok.
>>
>> Please find a more verbose log file of loading the kernel modules here:
>>
>> https://people.freebsd.org/~grembo/c720-20161105.log
On 05/10/2016 01:48, Michael Gmelin wrote:
> Double-checked the hints, it's all ok.
>
> Please find a more verbose log file of loading the kernel modules here:
>
> https://people.freebsd.org/~grembo/c720-20161105.log
Unfortunately this doesn't provide any new insights.
Could you please add
On Tue, 4 Oct 2016 13:07:28 +0300
Andriy Gapon wrote:
> On 04/10/2016 12:46, Michael Gmelin wrote:
> > iicbus(0|1) actually show up in devinfo -v, but nothing else works.
> >
> > You can find a log file and various outputs (dmesg, devinfo etc)
> > here:
> >
> >
On 04/10/2016 12:46, Michael Gmelin wrote:
> iicbus(0|1) actually show up in devinfo -v, but nothing else works.
>
> You can find a log file and various outputs (dmesg, devinfo etc) here:
>
> https://people.freebsd.org/~grembo/c720-20161104.log
Thank you.
Could you please double-check that
On Tue, 4 Oct 2016 01:04:10 +0300
Andriy Gapon wrote:
> On 03/10/2016 23:25, Michael Gmelin wrote:
> > On Mon, 3 Oct 2016 19:41:17 +0300
> > Andriy Gapon wrote:
> >
> >> On 03/10/2016 19:07, Michael Gmelin wrote:
> >>> I upgraded the latter the r306641,
On 03/10/2016 23:25, Michael Gmelin wrote:
> On Mon, 3 Oct 2016 19:41:17 +0300
> Andriy Gapon wrote:
>
>> On 03/10/2016 19:07, Michael Gmelin wrote:
>>> I upgraded the latter the r306641, applied your patches (cleanly)
>>> and ran "make kernel" (GENERIC kernel), added the
On Mon, 3 Oct 2016 19:41:17 +0300
Andriy Gapon wrote:
> On 03/10/2016 19:07, Michael Gmelin wrote:
> > I upgraded the latter the r306641, applied your patches (cleanly)
> > and ran "make kernel" (GENERIC kernel), added the entries to
> > device.hints and rebooted. Unfortunately
On 03/10/2016 19:07, Michael Gmelin wrote:
> I upgraded the latter the r306641, applied your patches (cleanly) and
> ran "make kernel" (GENERIC kernel), added the entries to device.hints
> and rebooted. Unfortunately ig4 won't load:
>
> # kldload ig4
> link_elf_obj: symbol iicbus_transfer_desc
On Mon, 3 Oct 2016 14:05:52 +0300
Andriy Gapon wrote:
> If you have a Chromebook where you are currently able to use isl and
> cyapa drivers, could you please test the following code change?
> https://people.freebsd.org/~avg/ig4-i2c.diff
>
> The change moves the drivers from
If you have a Chromebook where you are currently able to use isl and cyapa
drivers, could you please test the following code change?
https://people.freebsd.org/~avg/ig4-i2c.diff
The change moves the drivers from the SMBus to the I2C bus and as such some
configuration changes are required.
43 matches
Mail list logo