Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers

[Jayen Ashar]

What I have now is a set of instructions for building packages with
modass[1] which I've used for compat-wireless and peak's canbus
driver.  I would like to (at some point) learn to use dkms, especially
if it'll make my job easier.  I also welcome someone [a mentor] to
work with on this as my packaging skills are pretty hacky.

--Jayen

[1] I've been meaning to file a bug report to improve the HOWTO.Devel
but haven't gotten around to it.


On Thu, Aug 15, 2013 at 9:01 AM, Ben Hutchings  wrote:
>
> So we had a meeting at DebConf about improving hardware support in
> stable, and seemed to come to a consensus that compat-drivers (formerly
> compat-wireless) could be added to stable.  See
> .  (I forgot
> about this ITP bug, otherwise I would have cc'd it on that message.)
>
> compat-drivers would have to build binary debs for all kernel flavours
> and udebs for installer images.  This can be done with the help of the
> linux-support-3.2.0-4 and kernel-wedge packages.
>
> What is the status of your packaging work?  What do you think of this
> plan, and can I work with you on it?
>
> Ben.
>
> --
> Ben Hutchings
> Man invented language to satisfy his deep need to complain. - Lily Tomlin




-- 
Marathon Targets Pty Ltd
Marathon, like the run from Marathon to Athens
Targets, like the things at which one shoots for practice
Sydney, Australia
http://www.marathon-targets.com/


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cachadqtzun9ltq2y48eysuub+tlhihenrsaehpop-+8exy_...@mail.gmail.com

Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers

[Ben Hutchings]

So we had a meeting at DebConf about improving hardware support in
stable, and seemed to come to a consensus that compat-drivers (formerly
compat-wireless) could be added to stable.  See
.  (I forgot
about this ITP bug, otherwise I would have cc'd it on that message.)

compat-drivers would have to build binary debs for all kernel flavours
and udebs for installer images.  This can be done with the help of the
linux-support-3.2.0-4 and kernel-wedge packages.

What is the status of your packaging work?  What do you think of this
plan, and can I work with you on it?

Ben.

-- 
Ben Hutchings
Man invented language to satisfy his deep need to complain. - Lily Tomlin


signature.asc
Description: This is a digitally signed message part

Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers

[Ben Hutchings]

On Sat, 2012-12-22 at 20:36 +1100, Jayen Ashar wrote:
> On Sat, Dec 22, 2012 at 12:18 AM, Ben Hutchings  wrote:
> > On Mon, 2012-12-17 at 12:41 +1100, Jayen Ashar wrote:
> >> On Mon, Dec 17, 2012 at 12:07 PM, Ben Hutchings  
> >> wrote:
> >> > On Mon, 2012-12-17 at 11:14 +1100, Jayen Ashar wrote:
> >> >> Hi kernel team,
> >> >>
> >> >> I intend to package the stable versions of compat-wireless and
> >> >> compat-drivers (when available) as module-assistant packages, starting
> >> >> with compat-wireless 3.5.4.  The reason I am using module-assistant
> >> >> (instead of dkms) is so that embedded users of debian can compile &
> >> >> distribute kernel module packages without needing a compiler on the
> >> >> embedded device.
> >> >
> >> > This is not a reason to avoid DKMS, as you can use 'dkms mkdeb' to build
> >> > a package for installation elsewhere.
> >>
> >> didn't know about mkdeb.  will start looking at dkms (at least for our
> >> internal use).  thanks.
> >>
> >> >> I am starting with 3.5.4 because I have already
> >> >> packaged it for my company and have tested it internally with the
> >> >> squeeze kernel.
> >> >
> >> > Since wheezy is now frozen, this cannot be added to wheezy and therefore
> >> > cannot be added to squeeze-backports either.  So this will not be a very
> >> > effective way to help other squeeze users.
> >>
> >> Could it be added to wheezy-backports?
> >
> > Yes, once it's in testing for jessie.
> >
> >> > The official kernel package (linux-2.6/linux source package) does get
> >> > stable updates to extend hardware support, but not as many as I would
> >> > like.  I would really like to see compat-drivers integrated into the
> >> > linux source package so users don't need to look for extra package or a
> >> > special installer.  But we will need to ensure that there is adequate
> >> > regression testing whenever we update compat-drivers in stable.
> >> >
> >> > Would you be interesting in working on this?  It would help many more
> >> > users than a separate package.
> >>
> >> Are you asking for work on adding it to linux-source, or doing some
> >> testing?  I'm not sure I could provide adequate testing on any version
> >> other than the one's my company is running.
> >
> > I'm requesting that you work on adding it to the linux source package
> > and do what testing you can.  In any case we'll have to ask users for
> > beta testing.
> >
> > Before you do that work, though, it would need to be agreed among the
> > kernel and release teams that we should update drivers in this way.  But
> > I hope that's not too controversial.
> 
> Do you think there is value in having many versions available?
> (Ubuntu seems to have this.)  I was planning to separately package
> 3.3, 3.4, 3.5, and 3.6, so users could have the version they wanted.

Users will want the version that works, which they likely won't know in
advance.  We should take responsibility for picking a good version and
any necessary bug fixes on top of it.

Ben.

> (I was planning on earlier versions as well, but if there's no hope of
> getting into squeeze-backports, I see little purpose.)

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug


signature.asc
Description: This is a digitally signed message part

Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers

[Jayen Ashar]

On Sat, Dec 22, 2012 at 12:18 AM, Ben Hutchings  wrote:
> On Mon, 2012-12-17 at 12:41 +1100, Jayen Ashar wrote:
>> On Mon, Dec 17, 2012 at 12:07 PM, Ben Hutchings  wrote:
>> > On Mon, 2012-12-17 at 11:14 +1100, Jayen Ashar wrote:
>> >> Hi kernel team,
>> >>
>> >> I intend to package the stable versions of compat-wireless and
>> >> compat-drivers (when available) as module-assistant packages, starting
>> >> with compat-wireless 3.5.4.  The reason I am using module-assistant
>> >> (instead of dkms) is so that embedded users of debian can compile &
>> >> distribute kernel module packages without needing a compiler on the
>> >> embedded device.
>> >
>> > This is not a reason to avoid DKMS, as you can use 'dkms mkdeb' to build
>> > a package for installation elsewhere.
>>
>> didn't know about mkdeb.  will start looking at dkms (at least for our
>> internal use).  thanks.
>>
>> >> I am starting with 3.5.4 because I have already
>> >> packaged it for my company and have tested it internally with the
>> >> squeeze kernel.
>> >
>> > Since wheezy is now frozen, this cannot be added to wheezy and therefore
>> > cannot be added to squeeze-backports either.  So this will not be a very
>> > effective way to help other squeeze users.
>>
>> Could it be added to wheezy-backports?
>
> Yes, once it's in testing for jessie.
>
>> > The official kernel package (linux-2.6/linux source package) does get
>> > stable updates to extend hardware support, but not as many as I would
>> > like.  I would really like to see compat-drivers integrated into the
>> > linux source package so users don't need to look for extra package or a
>> > special installer.  But we will need to ensure that there is adequate
>> > regression testing whenever we update compat-drivers in stable.
>> >
>> > Would you be interesting in working on this?  It would help many more
>> > users than a separate package.
>>
>> Are you asking for work on adding it to linux-source, or doing some
>> testing?  I'm not sure I could provide adequate testing on any version
>> other than the one's my company is running.
>
> I'm requesting that you work on adding it to the linux source package
> and do what testing you can.  In any case we'll have to ask users for
> beta testing.
>
> Before you do that work, though, it would need to be agreed among the
> kernel and release teams that we should update drivers in this way.  But
> I hope that's not too controversial.

Do you think there is value in having many versions available?
(Ubuntu seems to have this.)  I was planning to separately package
3.3, 3.4, 3.5, and 3.6, so users could have the version they wanted.
(I was planning on earlier versions as well, but if there's no hope of
getting into squeeze-backports, I see little purpose.)

--Jayen

> Ben.
>
> --
> Ben Hutchings
> Make three consecutive correct guesses and you will be considered an expert.



--

Marathon Targets Pty Ltd
Sydney, Australia
http://www.marathon-targets.com/


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAChaDqRKEz88qpzeD8po3S9Scjpfr5vbuEkbjygwdHwOUwLR=q...@mail.gmail.com

Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers

[Ben Hutchings]

On Mon, 2012-12-17 at 12:41 +1100, Jayen Ashar wrote:
> On Mon, Dec 17, 2012 at 12:07 PM, Ben Hutchings  wrote:
> > On Mon, 2012-12-17 at 11:14 +1100, Jayen Ashar wrote:
> >> Hi kernel team,
> >>
> >> I intend to package the stable versions of compat-wireless and
> >> compat-drivers (when available) as module-assistant packages, starting
> >> with compat-wireless 3.5.4.  The reason I am using module-assistant
> >> (instead of dkms) is so that embedded users of debian can compile &
> >> distribute kernel module packages without needing a compiler on the
> >> embedded device.
> >
> > This is not a reason to avoid DKMS, as you can use 'dkms mkdeb' to build
> > a package for installation elsewhere.
> 
> didn't know about mkdeb.  will start looking at dkms (at least for our
> internal use).  thanks.
> 
> >> I am starting with 3.5.4 because I have already
> >> packaged it for my company and have tested it internally with the
> >> squeeze kernel.
> >
> > Since wheezy is now frozen, this cannot be added to wheezy and therefore
> > cannot be added to squeeze-backports either.  So this will not be a very
> > effective way to help other squeeze users.
> 
> Could it be added to wheezy-backports?

Yes, once it's in testing for jessie.

> > The official kernel package (linux-2.6/linux source package) does get
> > stable updates to extend hardware support, but not as many as I would
> > like.  I would really like to see compat-drivers integrated into the
> > linux source package so users don't need to look for extra package or a
> > special installer.  But we will need to ensure that there is adequate
> > regression testing whenever we update compat-drivers in stable.
> >
> > Would you be interesting in working on this?  It would help many more
> > users than a separate package.
> 
> Are you asking for work on adding it to linux-source, or doing some
> testing?  I'm not sure I could provide adequate testing on any version
> other than the one's my company is running.

I'm requesting that you work on adding it to the linux source package
and do what testing you can.  In any case we'll have to ask users for
beta testing.

Before you do that work, though, it would need to be agreed among the
kernel and release teams that we should update drivers in this way.  But
I hope that's not too controversial.

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an expert.


signature.asc
Description: This is a digitally signed message part

Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers

[Jayen Ashar]

On Mon, Dec 17, 2012 at 12:07 PM, Ben Hutchings  wrote:
> On Mon, 2012-12-17 at 11:14 +1100, Jayen Ashar wrote:
>> Hi kernel team,
>>
>> I intend to package the stable versions of compat-wireless and
>> compat-drivers (when available) as module-assistant packages, starting
>> with compat-wireless 3.5.4.  The reason I am using module-assistant
>> (instead of dkms) is so that embedded users of debian can compile &
>> distribute kernel module packages without needing a compiler on the
>> embedded device.
>
> This is not a reason to avoid DKMS, as you can use 'dkms mkdeb' to build
> a package for installation elsewhere.

didn't know about mkdeb.  will start looking at dkms (at least for our
internal use).  thanks.

>> I am starting with 3.5.4 because I have already
>> packaged it for my company and have tested it internally with the
>> squeeze kernel.
>
> Since wheezy is now frozen, this cannot be added to wheezy and therefore
> cannot be added to squeeze-backports either.  So this will not be a very
> effective way to help other squeeze users.

Could it be added to wheezy-backports?

> The official kernel package (linux-2.6/linux source package) does get
> stable updates to extend hardware support, but not as many as I would
> like.  I would really like to see compat-drivers integrated into the
> linux source package so users don't need to look for extra package or a
> special installer.  But we will need to ensure that there is adequate
> regression testing whenever we update compat-drivers in stable.
>
> Would you be interesting in working on this?  It would help many more
> users than a separate package.

Are you asking for work on adding it to linux-source, or doing some
testing?  I'm not sure I could provide adequate testing on any version
other than the one's my company is running.

Thanks,
Jayen

--

Marathon Targets Pty Ltd
Sydney, Australia
http://www.marathon-targets.com/


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAChaDqQk+Umccp_510qHx0=b4efdr2zg70scvoy3aa_av2y...@mail.gmail.com

Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers

[Ben Hutchings]

On Mon, 2012-12-17 at 11:14 +1100, Jayen Ashar wrote:
> Hi kernel team,
> 
> I intend to package the stable versions of compat-wireless and
> compat-drivers (when available) as module-assistant packages, starting
> with compat-wireless 3.5.4.  The reason I am using module-assistant
> (instead of dkms) is so that embedded users of debian can compile &
> distribute kernel module packages without needing a compiler on the
> embedded device.

This is not a reason to avoid DKMS, as you can use 'dkms mkdeb' to build
a package for installation elsewhere.

> I am starting with 3.5.4 because I have already
> packaged it for my company and have tested it internally with the
> squeeze kernel.

Since wheezy is now frozen, this cannot be added to wheezy and therefore
cannot be added to squeeze-backports either.  So this will not be a very
effective way to help other squeeze users.

The official kernel package (linux-2.6/linux source package) does get
stable updates to extend hardware support, but not as many as I would
like.  I would really like to see compat-drivers integrated into the
linux source package so users don't need to look for extra package or a
special installer.  But we will need to ensure that there is adequate
regression testing whenever we update compat-drivers in stable.

Would you be interesting in working on this?  It would help many more
users than a separate package.

Ben.

-- 
Ben Hutchings
Life is like a sewer:
what you get out of it depends on what you put into it.


signature.asc
Description: This is a digitally signed message part

Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers

[Jayen Ashar]

Hi kernel team,

I intend to package the stable versions of compat-wireless and
compat-drivers (when available) as module-assistant packages, starting
with compat-wireless 3.5.4.  The reason I am using module-assistant
(instead of dkms) is so that embedded users of debian can compile &
distribute kernel module packages without needing a compiler on the
embedded device.  I am starting with 3.5.4 because I have already
packaged it for my company and have tested it internally with the
squeeze kernel.

Thanks,
Jayen

On Sun, Dec 16, 2012 at 11:32 PM, Ben Hutchings  wrote:
> On Sun, 2012-12-16 at 15:10 +1100, Jayen Ashar wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Jayen Ashar 
>>
>> * Package name: compat-wireless-3.5.4
>>   Version : 1-snp
>
> This has been replaced by compat-drivers
> .
>
>>   Upstream Author : Linux Wireless team 
>> * URL : http://linuxwireless.org/
>> * License : This work is a subset of the Linux kernel as such we 
>> keep the kernel's Copyright practice. Some files have their own copyright 
>> and in those cases the license is mentioned in the file. All additional work 
>> made to building this package is licensed under the GPLv2.
>>   Programming Lang: C
>>   Description : backported linux wireless drivers
>>
>> These packages contain the source code of the wireless drivers from a newer
>> linux kernel.  These drivers have been backported to be compatible with
>> every kernel >= 2.6.26.  These packages allow building of binary packages
>> through the use of module-assistant.
>
> Please discuss this with the kernel team.
>
> Ben.
>
> --
> Ben Hutchings
> Always try to do things in chronological order;
> it's less confusing that way.



-- 

Marathon Targets Pty Ltd
Sydney, Australia
http://www.marathon-targets.com/


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cachadqtrcoujpbfx-wsviggu-6ssvyirf-nqhkgps0zq8km...@mail.gmail.com

Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers

[Ben Hutchings]

On Sun, 2012-12-16 at 15:10 +1100, Jayen Ashar wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Jayen Ashar 
> 
> * Package name: compat-wireless-3.5.4
>   Version : 1-snp

This has been replaced by compat-drivers
.

>   Upstream Author : Linux Wireless team 
> * URL : http://linuxwireless.org/
> * License : This work is a subset of the Linux kernel as such we keep 
> the kernel's Copyright practice. Some files have their own copyright and in 
> those cases the license is mentioned in the file. All additional work made to 
> building this package is licensed under the GPLv2. 
>   Programming Lang: C
>   Description : backported linux wireless drivers
> 
> These packages contain the source code of the wireless drivers from a newer
> linux kernel.  These drivers have been backported to be compatible with
> every kernel >= 2.6.26.  These packages allow building of binary packages
> through the use of module-assistant.

Please discuss this with the kernel team.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.


signature.asc
Description: This is a digitally signed message part