I am unfamiliar with how the repo. But it may be helpful to give an idea
what sort of conflicts there are? Maybe in a gist?
--Luther
On Friday, October 5, 2018 at 12:22:26 PM UTC+8, Enoch wrote:
>
> Hi Robert Nelson & Friends,
>
> I have a local Linux kernel repository that tracks
> g...@githu
I'll copy the group next time it occurs [as the last update I handled
through lazy cloning and then added my patches].
I guess Robert Nelson can answer as it must be related to the way he copies
his private kernel repository changes to the Beagleboard public.
Here are his latest two commit messa
On Fri, Oct 5, 2018 at 9:16 AM Enoch wrote:
>
> I'll copy the group next time it occurs [as the last update I handled through
> lazy cloning and then added my patches].
> I guess Robert Nelson can answer as it must be related to the way he copies
> his private kernel repository changes to the Be
Can you (somehow) make it easier to follow the public Beagleboard kernel
via the usual git-pull and git-rebase processes [to enter one's local
commits] .
*Your work is greatly appreciated. *The vanilla Linux-stable kernel is
simply inadequate to take advantage of the full Beagleboard hardware.
I
On Fri, Oct 5, 2018 at 9:47 AM Enoch wrote:
>
> Can you (somehow) make it easier to follow the public Beagleboard kernel via
> the usual git-pull and git-rebase processes [to enter one's local commits] .
> Your work is greatly appreciated. The vanilla Linux-stable kernel is simply
> inadequate t
Hi Matthew,
My comments here are based on WL18xx experience rather than BBBW
specifically.
For WL18xx to stay active while the host (AM335x) is suspended the WL_EN
pin needs to be kept high. However if I look at
am335x-boneblack-wl1835.dtsi (from 4.9.88-ti-rt-r107 which I happened to
have) I
This is how I do it:
git fetch beagleboard
git rebase --onto 4.14.71-ti-r79 4.14.71-ti-r78 my-branch
where "beagleboard" is the git remote for https://github.com/beagleboard/linux.git,
"4.14.71-ti-r79" is the new tag I am rebasing onto, "4.14.71-ti-r78" is the previous tag my branch
was base
Hello
I have been trying to configurate the GPIO’s as inputs , using this code (
I just show the main section).
*import Adafruit_BBIO.GPIO as GPIO.*
*DOOR= "P9_15" *
*GPIO.setup(DOOR, GPIO.IN)*
*print ( “test”)*
However, I get an error message.
*Traceback (most recent call last):*
*File "/v
So looking at:
https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201720180SB327
**
SECTION 1. Title 1.81.26 (commencing with Section 1798.
Hello,
Your instructions worked very well on a Debian 7 but things changed on
Debian 9.
Do you have updated instructions?
I can only get some default splash-screen with 3 dots.
Thanks,
Ademar
quarta-feira, 22 de Outubro de 2014 às 14:34:51 UTC+1, R3DP escreveu:
>
> Hello,
>
> I know it'
The unique password requirement applies in the case where "a connected
device is equipped with a means for authentication outside a local area
network" which a beaglebone does not unless the user manually forwards
ports on their router, which could be argued as the user intentionally
compromising t
On Fri, Oct 5, 2018 at 3:31 PM James Strawson wrote:
>
> The unique password requirement applies in the case where "a connected device
> is equipped with a means for authentication outside a local area network"
> which a beaglebone does not unless the user manually forwards ports on their
> rou
12 matches
Mail list logo
