> Date: Sat, 30 Jul 2022 18:45:39 +0300
> From: Vitaliy Makkoveev
>
> On Wed, Jul 27, 2022 at 08:53:38PM +0200, Mark Kettenis wrote:
> > > Date: Wed, 27 Jul 2022 00:11:19 +0200
> > > From: Alexander Bluhm
> > >
> > > On Tue, Jul 26, 2022 at 11:19:27PM +0200, Mark Kettenis wrote:
> > > > > Date:
On Wed, Jul 27, 2022 at 08:53:38PM +0200, Mark Kettenis wrote:
> > Date: Wed, 27 Jul 2022 00:11:19 +0200
> > From: Alexander Bluhm
> >
> > On Tue, Jul 26, 2022 at 11:19:27PM +0200, Mark Kettenis wrote:
> > > > Date: Tue, 26 Jul 2022 18:11:01 +0200
> > > > From: Alexander Bluhm
> > > >
> > > > On
> Date: Wed, 27 Jul 2022 00:11:19 +0200
> From: Alexander Bluhm
>
> On Tue, Jul 26, 2022 at 11:19:27PM +0200, Mark Kettenis wrote:
> > > Date: Tue, 26 Jul 2022 18:11:01 +0200
> > > From: Alexander Bluhm
> > >
> > > On Fri, Jul 22, 2022 at 06:13:04PM +0200, Alexander Bluhm wrote:
> > > > But I am
On Tue, Jul 26, 2022 at 11:19:27PM +0200, Mark Kettenis wrote:
> > Date: Tue, 26 Jul 2022 18:11:01 +0200
> > From: Alexander Bluhm
> >
> > On Fri, Jul 22, 2022 at 06:13:04PM +0200, Alexander Bluhm wrote:
> > > But I am fine with committing ifmedia, gem(4) and bge(4) now. Then
> > > we can decide
> Date: Tue, 26 Jul 2022 18:11:01 +0200
> From: Alexander Bluhm
>
> On Fri, Jul 22, 2022 at 06:13:04PM +0200, Alexander Bluhm wrote:
> > But I am fine with committing ifmedia, gem(4) and bge(4) now. Then
> > we can decide on a per driver basis. As long kernel lock is not
> > removed from the if
On Tue, Jul 26, 2022 at 06:11:01PM +0200, Alexander Bluhm wrote:
> On Fri, Jul 22, 2022 at 06:13:04PM +0200, Alexander Bluhm wrote:
> > But I am fine with committing ifmedia, gem(4) and bge(4) now. Then
> > we can decide on a per driver basis. As long kernel lock is not
> > removed from the ifmed
ok by me
> On 26 Jul 2022, at 19:11, Alexander Bluhm wrote:
>
> On Fri, Jul 22, 2022 at 06:13:04PM +0200, Alexander Bluhm wrote:
>> But I am fine with committing ifmedia, gem(4) and bge(4) now. Then
>> we can decide on a per driver basis. As long kernel lock is not
>> removed from the ifmedia
On Fri, Jul 22, 2022 at 06:13:04PM +0200, Alexander Bluhm wrote:
> But I am fine with committing ifmedia, gem(4) and bge(4) now. Then
> we can decide on a per driver basis. As long kernel lock is not
> removed from the ifmedia layer, this diff is not strictly necessary.
> I want to commit it anyw
On Fri, Jul 22, 2022 at 05:44:52PM +0200, Mark Kettenis wrote:
> > Date: Fri, 22 Jul 2022 17:01:20 +0200
> > From: Alexander Bluhm
> >
> > On Fri, Jul 15, 2022 at 04:51:25PM +0200, Alexander Bluhm wrote:
> > > On Fri, Jul 15, 2022 at 02:05:40AM +0200, Alexander Bluhm wrote:
> > > > If anyone has
> Date: Fri, 22 Jul 2022 17:01:20 +0200
> From: Alexander Bluhm
>
> On Fri, Jul 15, 2022 at 04:51:25PM +0200, Alexander Bluhm wrote:
> > On Fri, Jul 15, 2022 at 02:05:40AM +0200, Alexander Bluhm wrote:
> > > If anyone has some of these old network drivers, please test setting
> > > media type wit
On Fri, Jul 15, 2022 at 04:51:25PM +0200, Alexander Bluhm wrote:
> On Fri, Jul 15, 2022 at 02:05:40AM +0200, Alexander Bluhm wrote:
> > If anyone has some of these old network drivers, please test setting
> > media type with ifconfig.
>
> Updated diff. I have compile tested it on amd64, i386, oct
On Fri, Jul 15, 2022 at 02:05:40AM +0200, Alexander Bluhm wrote:
> If anyone has some of these old network drivers, please test setting
> media type with ifconfig.
Updated diff. I have compile tested it on amd64, i386, octeon,
macppc, sparc64. Setting media for gem(4) and bge(4) works.
bluhm
I
Hi,
Instead of reading the unprotected pointer ifm_cur, drivers use API
to access current media and data. New function ifmedia_current()
provides read access with mutex locking.
If anyone has some of these old network drivers, please test setting
media type with ifconfig.
ok?
bluhm
Index: arc
13 matches
Mail list logo
