On 2020-03-13 18:31, Stuart Henderson wrote:
On 2020-03-13, Jordan Geoghegan wrote:
I wouldn't get too excited about running on low memory machines. The
more RAM you can throw at something, the better, as this allows more
cache room as well as improving function of ASLR and other memory
On 2020-03-13, Jordan Geoghegan wrote:
>
>
> On 2020-03-13 09:50, Christian Weisgerber wrote:
>> On 2020-03-13, "Peter J. Philipp" wrote:
>>
>>> Any developer working on a riscv port and willing to share their unofficial
>>> work for possible future collaboration?
>> I think I'd have heard by
On 2020-03-13, Jordan Geoghegan wrote:
> I wouldn't get too excited about running on low memory machines. The
> more RAM you can throw at something, the better, as this allows more
> cache room as well as improving function of ASLR and other memory
> randomizations.
It does allow more cache,
Hi Chris,
Chris Bennett wrote on Fri, Mar 13, 2020 at 08:23:22PM -0400:
> Thanks, that was helpful.
> I did not think of using info cvs. I do use info at times,
> just not that often.
That is quite understandable. With BSD systems in general, it is
both the normal case and also our goal that
Thanks, that was helpful.
I did not think of using info cvs. I do use info at times, just not that
often.
I'm just using CVS for porting. Since -current offers a tar file and
I've made a partition for /usr/ports and another for /usr/ports/mystuff,
so I'm just using that file to replace ports
Hi Chris,
Chris Bennett wrote on Fri, Mar 13, 2020 at 04:47:09PM -0400:
> I am running -current.
>
> On one server, src was empty. So I did a cvs checkout.
> On another server, src had older files. So I did a cvs up.
>
> Afterwards, inttypes.h had one size on the checkout, another size on the
On 2020-03-11 19:20, Aaron Mason wrote:
On Wed, Mar 11, 2020 at 6:47 PM Jordan Geoghegan wrote:
On 2020-03-11 00:13, Stuart Longland wrote:
On 15/2/20 6:43 pm, Dumitru Moldovan wrote:
[SNIP]
[SNIP]
Sometimes it's better to realise when something has past its prime.
A year or two ago
On 2020-03-13 09:50, Christian Weisgerber wrote:
On 2020-03-13, "Peter J. Philipp" wrote:
Any developer working on a riscv port and willing to share their unofficial
work for possible future collaboration?
I think I'd have heard by now if somebody was, so I'll go out on a
limb and say no,
I am running -current.
On one server, src was empty. So I did a cvs checkout.
On another server, src had older files. So I did a cvs up.
Afterwards, inttypes.h had one size on the checkout, another size on the
updated src.
I rm'ed the updated src and did a checkout. Now both files are the same
Hi misc@,
I have recently tested OpenBSD 6.6-current (11.03.2020) on the TUXEDO
InfinityBook Pro 14 v5 laptop. While the synaptics touchpad is not detected on
OpenBSD, it works fine on Linux -- please find below the corresponding dmesg
lines:
[ 14.485208] psmouse serio2: synaptics: queried
On Fri, 13 Mar 2020 16:41:41 +0100
Patrick Wildt wrote:
> On Fri, Mar 13, 2020 at 12:12:18PM +0100, Rob Schmersel wrote:
> > Hello,
> >
> > In order to use a SDIO based bwfm device a "NVRAM" configuration
> > file will be needed besides the firmware file. This configuration
> > file is expected
On 2020-03-13, "Peter J. Philipp" wrote:
> Any developer working on a riscv port and willing to share their unofficial
> work for possible future collaboration?
I think I'd have heard by now if somebody was, so I'll go out on a
limb and say no, nobody's working on a RISC-V port.
--
Christian
On Fri, Mar 13, 2020 at 12:12:18PM +0100, Rob Schmersel wrote:
> Hello,
>
> In order to use a SDIO based bwfm device a "NVRAM" configuration file
> will be needed besides the firmware file. This configuration file is
> expected to be in the /etc/firmware directory, in the form of
>
On Fri, 13 Mar 2020 13:41:48 +0100
Stefan Sperling wrote:
> On Fri, Mar 13, 2020 at 12:12:18PM +0100, Rob Schmersel wrote:
> > Question: Are there plans to include the NVRAM files in
> > bwfm_firmware package?
>
> Yes, this is being worked on. See these recent commits by Patrick:
>
On Fri, Mar 13, 2020 at 12:12:18PM +0100, Rob Schmersel wrote:
> Question: Are there plans to include the NVRAM files in bwfm_firmware
> package?
Yes, this is being worked on. See these recent commits by Patrick:
https://marc.info/?l=openbsd-cvs=158357502421524=2
Hello,
In order to use a SDIO based bwfm device a "NVRAM" configuration file
will be needed besides the firmware file. This configuration file is
expected to be in the /etc/firmware directory, in the form of
brcmfmac{chip}-sdio.txt OR brcmfmac{chip}-sdio.nvram
The need for this configuration
Le 13/03/2020 à 13:23, Raf Czlonka a écrit :> Hi David,
hotplugd(8) might help here.
Thanks, I've heard of it in the past. Can't understand how I did forget
it. That will help me a lot!
Regards,
--
David
On Fri, Mar 13, 2020 at 12:13:45PM GMT, David Demelier wrote:
> Hello,
>
> I'm using trunk(4) pseudo device to aggregate my wireless iwm(4) and my
> dock ethernet interface ure(4) together.
>
> Since my laptop is not always connected to my dock, when booting I get a
> trunk error if the
Hello,
I'm using trunk(4) pseudo device to aggregate my wireless iwm(4) and my
dock ethernet interface ure(4) together.
Since my laptop is not always connected to my dock, when booting I get a
trunk error if the interface is not available:
ifconfig: SIOCTRUNKPORT: Invalid argument
Any developer working on a riscv port and willing to share their unofficial
work for possible future collaboration?
Best Regards,
-peter
Depends on your app, if your software is working fine on it since years then
just leave it as is. You don't want multiarch systems it is even a mess in
linux. A system like that should not be upgraded but migrated, you setup a
clean install with the latest 64bit Obsd on another machine then
21 matches
Mail list logo