Hi there,
Since around 2022-11, I am unable to change display brightness
of the display of a Framework laptop (Intel i5-1135G7, Iris
Xe iGPU) with "i915kms" module (from "drm-510-kmod" package/port)
& "acpi_video" (FreeBSD) kernel module.
Earlier I was able to change brightness via "hw.acpi.video
My two cents...
I think some of the integration issues can be resolved with some rule
changes and showing those relevant rules that people will see every time
they make a pull request, report, etc... as I think what will happen with
each item is too uncertain even if there was automation. I think
El lun., 30 ene. 2023 18:06, ykla escribió:
> Hi,
>
> The documentation project on reviews.freebsd.org is also very inactive.
> For example, it's been almost 3 months since I submitted my revision -
> https://reviews.freebsd.org/D37322. After I submitted it, it was neither
> reviewed nor approved
Maybe, but my laziness won't let me keep it that simple :)
https://reviews.freebsd.org/H185 should do the trick, I think.
Warner Losh writes:
> I think just "sys/dev/dpaa2" is all you need when adding the Herald rule. :)
>
> More generally, no, there's no way that I've found to only match file
On 1/30/23 13:32, User Ngor wrote:
On 1/30/23 13:53, Warner Losh wrote:
On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote:
Hi,
On 1/30/23 02:54, Julian H. Stacey wrote:
The main idea: to prevent information fragmentation and improve
discoverability, cross-referencing abilities
On 1/30/23 13:53, Warner Losh wrote:
On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote:
Hi,
On 1/30/23 02:54, Julian H. Stacey wrote:
The main idea: to prevent information fragmentation andimprove
discoverability, cross-referencing abilities, search, etc.
With regards to improvi
Hi,
The documentation project on reviews.freebsd.org is also very inactive. For
example, it's been almost 3 months since I submitted my revision -
https://reviews.freebsd.org/D37322. After I submitted it, it was neither
reviewed nor approved for a long time. Now, due to changes in the FreeBSD
docu
On 1/30/23 10:08, Kurt Jaeger wrote:
Hi!
ihor@antonovs.family wrote:
This can be as easy as moving everything into Phabricator.
There's the issue that Phabricator itself is no longer supported
upstream:
https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/
http
I think just "sys/dev/dpaa2" is all you need when adding the Herald rule. :)
More generally, no, there's no way that I've found to only match files that
match certain regexp.
Warner
On Mon, Jan 30, 2023 at 9:49 AM Dmitry Salychev wrote:
>
> Warner Losh writes:
>
> > On Mon, Jan 30, 2023 at 7:
Warner Losh writes:
> On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev wrote:
>
> Hi,
>
> Kurt Jaeger writes:
>
> > Hi,
> >
> >> > On 1/30/23 02:54, Julian H. Stacey wrote:
> >> >The main idea: to prevent information fragmentation andimprove
> >> >discoverability, cross-refe
Hi folks,
I'd like to first of all thank Warner for all his hard work. Working on
infrastructure can seem like pretty thankless work.
As an outsider to FreeBSD, but not an outsider to the workings of FLOSS
organisations, I just want to remind everyone of one core issue: It's usually
insiders,
On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev wrote:
>
> Hi,
>
> Kurt Jaeger writes:
>
> > Hi,
> >
> >> > On 1/30/23 02:54, Julian H. Stacey wrote:
> >> >The main idea: to prevent information fragmentation andimprove
> >> >discoverability, cross-referencing abilities, search, etc.
I think this was fixed by a commit yesterday.
rick
On Mon, Jan 30, 2023 at 6:51 AM qroxana wrote:
>
> /etc/rc failed to run "mount -uw /" when booting from NFS root,
> this happened after the commit 906c312bbf7493ccbcce883936d67e5c66a9c3c2,
> the previous commit works fine.
>
> + mount -uw /
> a
/etc/rc failed to run "mount -uw /" when booting from NFS root,
this happened after the commit 906c312bbf7493ccbcce883936d67e5c66a9c3c2,
the previous commit works fine.
+ mount -uw /
af 1 sotype 1 not supported
+ echo 'Mounting root filesystem rw failed, startup aborted'
Mounting root filesystem r
Warner Losh writes:
> On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote:
>
> Hi,
>
> > > On 1/30/23 02:54, Julian H. Stacey wrote:
> > >The main idea: to prevent information fragmentation andimprove
> > >discoverability, cross-referencing abilities, search, etc.
> >
> > With
Kurt Jaeger writes:
If you know phabricator in more detail, is there any kind of
tool to understand the activity going on ?
In bugs.freebsd.org, there is the dashboard:
https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html
I think we might need something similar to help us understan
Hi,
Kurt Jaeger writes:
> Hi,
>
>> > On 1/30/23 02:54, Julian H. Stacey wrote:
>> >The main idea: to prevent information fragmentation andimprove
>> >discoverability, cross-referencing abilities, search, etc.
>>
>> With regards to improving discoverability, Phabricator's Owner
>>
On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote:
> Hi,
>
> > > On 1/30/23 02:54, Julian H. Stacey wrote:
> > >The main idea: to prevent information fragmentation andimprove
> > >discoverability, cross-referencing abilities, search, etc.
> >
> > With regards to improving discoverabil
Hi,
> > On 1/30/23 02:54, Julian H. Stacey wrote:
> >The main idea: to prevent information fragmentation andimprove
> >discoverability, cross-referencing abilities, search, etc.
>
> With regards to improving discoverability, Phabricator's Owner
> tool could be a good tactical move: it
Hello,
> I had a similar thing happen to me, the mailing list FreeBSD-doc seemed to
> exist as if no one existed, and there was no one posting in it except for
> the automated bug reports from the bots.
> I have not had any replies to my several posts either.
> So can the admins tell how many peo
Hi,
I had a similar thing happen to me, the mailing list FreeBSD-doc seemed to
exist as if no one existed, and there was no one posting in it except for
the automated bug reports from the bots. I have not had any replies to my
several posts either. So can the admins tell how many people actually
s
Hi!
ihor@antonovs.family wrote:
> This can be as easy as moving everything into Phabricator.
There's the issue that Phabricator itself is no longer supported
upstream:
https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/
https://github.com/phacility/phabricator
User Ngor writes:
On 1/30/23 02:54, Julian H. Stacey wrote:
The main idea: to prevent information fragmentation and
improve
discoverability, cross-referencing abilities, search, etc.
With regards to improving discoverability, Phabricator's Owner
tool could be a good tactical move
23 matches
Mail list logo
