RPi 2 with 7-inch touchscreen.

[Oleksandr Tymoshenko]

> On Mar 28, 2016, at 12:08 PM, Mark R V Murray <markm at FreeBSD.org> wrote:
> 
> (Sorry about the email flood in may last reply - the email client was misbehaving)
> 
>> On 28 Mar 2016, at 19:48, Oleksandr Tymoshenko <gonzo at bluezbox.com> wrote:
>> 
>> 
>> Try copying firmware files from raspbian image as this comment suggests:
>> http://kernelnomicon.org/?p=540#comment-40186
>> 
>> Port may have older firmware, can't check right now.
> 
> That worked, once I commented out the "start_x=1" :-)
> 
> Thanks! :-)

No problem :) 

>>>> I also had touchscreen driver prototype working for it but can't find it at the moment :(
>>>> It's very simple busy read from memory window. Requires FDT modification and
>>>> interface to userland which FreeBSD does not have at the moment.
>>>> 
>>> 
>>> That's next on my list :-)
>> 
>> I'll try to dig up the driver later today. If I haven't deleted it during last "cleanup" that is :-/
> 
> Yes please!

https://people.freebsd.org/~gonzo/arm/bcm2835_ft5406.c
It's not pretty. You can use it as a reference. It implements home-made 
evdev-like API I used for testing with hacked-up version of tslib: 
https://github.com/gonzoua/experimental-freebsd-ports/tree/master/devel/tslib


> 
> Do you know how to make the USB keyboard work from the get-go? Mine works, but only *after* boot, so I can't interact with the boot process.

With u-boot from ports it's not possible. It has very basic USB support 
which does not include SPLIT commands required to communicate
with keyboard. There is Stephen Warren's version of u-boot, last time
I checked it did support keyboard. But in order to make it work with 
ubldr you'll need to change default configuration and add API support
+ some API fixes. If you don't want to go that way you have two options:
- Use serial console to communicate with u-boot if you really need 
    interactive boot process.
- Just put your custom logic to bootcmd in uEnv.txt if it's once-configure
    run-always thing.