There is no porting. You simply compile it with the proper device tree
version. Which is different from the version used for 3.8.x.

http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/

On Mon, Dec 7, 2015 at 5:21 PM, Matt Maher Peterson <
[email protected]> wrote:

> Yes I could but I have a custom device tree written to work in the old
> world of 3.18.3 Is there a simple way to port that into 4.1.13.ti.r35 ?
>
> On Monday, December 7, 2015 at 4:19:49 PM UTC-8, RobertCNelson wrote:
>>
>> On Mon, Dec 7, 2015 at 6:15 PM, Matt Maher Peterson
>> <[email protected]> wrote:
>> > Thanks Robert.
>> >
>> > I found the file and everything seams legit.  The real issue I was
>> trying to
>> > solve was that when plugging this device in to the USB input I was not
>> > getting the corresponding /dev/USBX's.
>> >
>> > After doing a
>> > modprobe option
>> > echo 1bc7 1201 > /sys/bus/usb-serial/drivers/option1/new_id
>> >
>> > I now see my /dev/USB1 thru /dev/USB6
>> >
>> > Why do I have to do these manual commands?  I guess I can scripts these
>> on
>> > boot but is there a better option.
>>
>> Well, you don't have to run 3.8.x:
>>
>>
>> https://github.com/beagleboard/linux/blob/4.1.13-ti-r35/drivers/usb/serial/option.c#L266-L274
>>
>> Run "4.1.13-ti-r35" and it'll just work. ;)
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to