As of U-Boot 2018.03 the mx6cuboxi U-Boot image may attempt to load
imx6q-hummingboard2.dtb
imx6dl-hummingboard2.dtb
imx6q-hummingboard.dtb
imx6dl-hummingboard.dtb
imx6q-cubox-i.dtb
imx6dl-cubox-i.dtb
dtbs for rev 1.5 soms will be loaded automatically at some
point in the future
On Wed, Mar 14, 2018 at 02:58:14PM +0100, Patrick Wildt wrote:
> Hi,
>
> I have some hardware where IPMI is not found using the SMBIOS table
> anymore but using ACPI. These show up in the dmesg as
>
> "IPI0001" at acpi0 not configured
>
> The driver basically reads the information out of ACPI
Hi,
I have some hardware where IPMI is not found using the SMBIOS table
anymore but using ACPI. These show up in the dmesg as
"IPI0001" at acpi0 not configured
The driver basically reads the information out of ACPI and then runs
the normal IPMI attach code. It's an attachment driver, no
OK florian@ for after unlock
On Tue, Mar 13, 2018 at 05:40:24PM -0400, David Hill wrote:
> Hello -
>
> A few bcopy to memcpy conversions where the memory does not overlap.
>
> OK?
>
> Index: netinet6/icmp6.c
> ===
> RCS file:
ok
Florian Obser(flor...@openbsd.org) on 2018.03.14 08:15:35 +0100:
> On Wed, Mar 14, 2018 at 01:08:33AM +, Stuart Henderson wrote:
> > On 2018/03/11 17:52, Florian Obser wrote:
> > >
> > > I think we should just follow the 301.
> >
> > I didn't hear back from @letsencrypt_ops about why
Hi,
This diff removes an unused member sc_iface_number of the softc. Ok?
Index: sys/dev/usb/uticom.c
===
RCS file: /cvs/src/sys/dev/usb/uticom.c,v
retrieving revision 1.32
diff -u -p -u -p -r1.32 uticom.c
--- sys/dev/usb/uticom.c
On Wed, Mar 14, 2018 at 01:08:33AM +, Stuart Henderson wrote:
> On 2018/03/11 17:52, Florian Obser wrote:
> >
> > I think we should just follow the 301.
>
> I didn't hear back from @letsencrypt_ops about why they were
> issue 301s, but I do agree it makes sense to follow them.
update diff
