Hi,
The diff below enables umb(4) support for SIMCom SIM7600.
The SIM7600 is a mbim compatible chip, you'll need to switch it into mbim
mode via specific AT-commands (AT+CUSBPIDSWITCH=9003,1,1 and AT+CLANMODE=1)
over the serial port.
umb0 at uhub1 port 2 "SIMCOM INCORPORATED SimTech,
Matthew Martin wrote:
> On Tue, May 18, 2021 at 10:24:00PM -0500, Matthew Martin wrote:
> > Sync the DNS types with IANA[1] and upstream[2]. With this the Type65
> > queries show up as HTTPS.
> >
> > Removed the UNSPECA type parsing as IANA has that query type number
> > assigned to NID now.
>
On Tue, May 18, 2021 at 10:24:00PM -0500, Matthew Martin wrote:
> Sync the DNS types with IANA[1] and upstream[2]. With this the Type65
> queries show up as HTTPS.
>
> Removed the UNSPECA type parsing as IANA has that query type number
> assigned to NID now.
>
> Also added a const on
On Thu, Sep 23, 2021 at 09:21:46PM +0100, Stuart Henderson wrote:
> (the extra register used by PIE > hurts i386 mode a lot more than amd64
> mode with its extra registers),
Just for the sake of correctness: it hurts much less on x86_64, because
there is IP-relative addressing for code *and*
rpki-client 7.3 has just been released and will be available in the
rpki-client directory of any OpenBSD mirror soon.
rpki-client is a FREE, easy-to-use implementation of the Resource
Public Key Infrastructure (RPKI) for Relying Parties (RP) to
facilitate validation of the Route Origin of a BGP
You've made a pretty big assumption there.
When we see something we don't think is important, we delete the
email and carry on with more important things.
You think hand-tuning this one paragraph is going to reduce the amount
of mail we delete because it doesn't matter? It won't.
A large
Because you might not wish to deal with people like me posting dmesg's
of absurdly deficient hardware on the lists. Putting minimum values up
means you can cast off everything you don't want to bother trying to
support as 'not worth your time', without anyone else having to
discover that it
Stuart Henderson wrote:
> Nobody should really by using i386 for new systems. The advantages
> of running amd64-compatible hardware are too big to ignore. Lower power
> consumption, much faster in most cases (the extra register used by PIE
> hurts i386 mode a lot more than amd64 mode with its
Nobody should really by using i386 for new systems. The advantages
of running amd64-compatible hardware are too big to ignore. Lower power
consumption, much faster in most cases (the extra register used by PIE
hurts i386 mode a lot more than amd64 mode with its extra registers),
more address space
Le Thu, 23 Sep 2021 14:37:12 +0200,
Janne Johansson a écrit :
> Den tors 23 sep. 2021 kl 14:27 skrev Patrick Harper :
> >
> > If there will continue to be a minimum disk value then 600MB wouldn't
> > be nearly enough for swap, maybe 2GB for a whole disk?
>
> Could this handwaving please stop?
Hi,
The bug details and corresponding patch can be referred to
https://github.com/libressl-portable/openbsd/issues/126
Best,
Zhengxiong Luo
On Thu, Sep 23, 2021 at 8:37 AM Janne Johansson wrote:
> Could this handwaving please stop? If anyone wants, make a i386 VM and
> do a binary search and record the minimums.
>
I have done this exercise, but not for kernel relinking -- it was for doing
full system rebuilds.
Starting with
Den tors 23 sep. 2021 kl 14:27 skrev Patrick Harper :
>
> If there will continue to be a minimum disk value then 600MB wouldn't
> be nearly enough for swap, maybe 2GB for a whole disk?
Could this handwaving please stop? If anyone wants, make a i386 VM and
do a binary search and record the
If there will continue to be a minimum disk value then 600MB wouldn't
be nearly enough for swap, maybe 2GB for a whole disk?
--
Patrick Harper
paia...@fastmail.com
On Thu, 23 Sep 2021, at 11:29, Zé Loff wrote:
> IMHO, stating minimum disk space requirements might be useful for
>
On Thu, Sep 23, 2021 at 11:29:53AM +0100, Zé Loff wrote:
> On Wed, Sep 22, 2021 at 05:27:30PM +0100, Patrick Harper wrote:
> > If the situation isn't going to change anytime soon then I have some
> > diffs for INSTALL.i386 and INSTALL.amd64. The latter has not specified
> > disk requirements, I
On Wed, Sep 22, 2021 at 05:27:30PM +0100, Patrick Harper wrote:
> If the situation isn't going to change anytime soon then I have some
> diffs for INSTALL.i386 and INSTALL.amd64. The latter has not specified
> disk requirements, I guess since anyone who owns an amd64 system will
> very likely
We have released OpenBGPD 7.2, which will be arriving in the
OpenBGPD directory of your local OpenBSD mirror soon.
This release includes the following changes to the previous release:
* Support for RFC 9072 - Extended Optional Parameters Lenght for
BGP OPEN Message
* Support for
17 matches
Mail list logo
