-Box
Signed-off-by: Karl Palsson
---
arch/arm/boot/dts/Makefile| 1 +
arch/arm/boot/dts/sun8i-h3-nanopi-duo2-iotbox.dts | 45 +++
2 files changed, 46 insertions(+)
create mode 100644 arch/arm/boot/dts/sun8i-h3-nanopi-duo2-iotbox.dts
diff --git a/arch
uart1 and uart3 had existing pin definitions for the rts/cts pairs.
Add definitions for uart2 as well.
Signed-off-by: Karl Palsson
---
arch/arm/boot/dts/sunxi-h3-h5.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/sunxi-h3-h5.dtsi
b/arch/arm/boot/dts/sunxi-h3-h5
This is an Allwinner H3 based board, with 512MB ram, a USB OTG port,
microsd slot, an onboard AP6212A wifi/bluetooth module, and a CSI
connector.
Full details and schematic available from vendor:
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_Duo2
Signed-off-by: Karl Palsson
---
arch/arm
Sorry if you get this twice, I was having some client problems,
but wanted to make sure you got this one...
Grigori Goronzy wrote:
> With the new reinitialization method, configuring parity,
> different frame lengths and different stop bit settings work as
> expected on both CH340G and CH341A. T
Grigori Goronzy wrote:
> The status bit was found with USB captures of the Windows
> driver and some luck. Tested on CH340G and CH341A.
By my reversing, bit 0x4, is "multiple status changes since last
interrupt"
>
> Signed-off-by: Grigori Goronzy
> ---
> drivers/usb/serial/ch341.c | 19 +
Grigori Goronzy wrote:
> With the new reinitialization method, configuring parity,
> different frame lengths and different stop bit settings work as
> expected on both CH340G and CH341A. This has been extensively
> tested with a logic analyzer.
>
> Tested-by: Ryan Barber
> Signed-off-by: Grigor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> > I admit I hadn't seen this earlier, and I didn't spend all day
> > looking at previous attempts, but what's the motivation for
> > putting all this overloaded syntax into the "brightness" file? I
> > thought the point was to have a single value in
s entry should do?
I'd like to set the rgb colour of a led (or hsv, that can be it's
own file too) and separately ramp the brightness up and down. I
also think it's substantially simpler and easier to use from the
user's point of view, which is surely the place you want easy
right
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Douglas Anderson wrote:
>
> + /*
> + * Sleep for 10-15 ms after the reset to let it finish.
> + *
> + * It's been confirmed on at least one version of the controller
> + * that this is a requirement that this is a requirement
nsible for them? Or alternatively, is userspace _meant_ to
be handling this directly from the "change" events? I see that
with a CD-ROM, there are no kernel add/remove events, only change
events, unlike SD cards.
Sincerely,
Karl Palsson
[1] Using the "in kernel" event polling with &q
Johan Hovold wrote:
> On Mon, Dec 08, 2014 at 05:24:17PM -0600, George McCollister wrote:
> > + newline.bParityType = termios->c_cflag & PARENB ?
> > + (termios->c_cflag & PARODD ? 1 : 2) +
> > + (termios->c_cflag & CMSPAR ? 2 : 0) : 0;
>
>
2cdetect results my first thought would have
> >been "are there pullups on the bus?".
> >
> >Cheers,
> > Max
> >
> >Am Mittwoch, 29. Oktober 2014, 13:44:15 schrieb Karl Palsson:
> >>I'd be more inclined to have pulls disabled by default, i
ect, without having to turn off things that are not default
anyway.
Sincerely,
Karl Palsson
On Wed, Oct 29, 2014 at 02:17:23PM +0100, Heiko Stübner wrote:
> Hi Addy, Max, Wolfram,
>
> after Doug's explanation of disfavour [0] and Julien's subsequent response I'm
> not
13 matches
Mail list logo
