Original Message
Subject: Questions abount driver development and Geniatech X9320
DVB-S/S2 PCIe Tuner
Date: 2020-11-02 10:38
From: m.bert...@pe2mbs.nl
To: Linux Media
Hi,
I'm trying to get Geniatech X9320 DVB-S/S2 PCIe Quad Tuner card working,
but i'm new to li
An update: see there:
http://ffmpeg.org/pipermail/ffmpeg-devel/2015-July/175796.html
--
Bluecherry developer.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-
An update with a request for help.
Asking for help with h264 headers generation. Both copying headers
from similar videos and porting headers generation code from reference
driver don't work for me (ref driver is weird and very complicated, so
porting involved importing of lots of code, but still
On Fri, Jul 3, 2015 at 5:23 PM, Andrey Utkin
wrote:
> Up... we are moving much slower than we expected, desperately needing help.
>
> Running reference driver with Ubuntu 9 (with kernel 2.6.28.10) with
> 16-port card shows that the
> reference driver fails to work with it correctly. Also that driv
On Wed, Jun 3, 2015 at 1:03 AM, Andrey Utkin
wrote:
> Hi! I am working on making a Linux driver for TW5864-based video&audio
> capture and encoding PCI boards. The driver is to be submitted for
> inclusion to Linux upstream.
> The following two links are links to boards available for buying:
> htt
Hi! I am working on making a Linux driver for TW5864-based video&audio
capture and encoding PCI boards. The driver is to be submitted for
inclusion to Linux upstream.
The following two links are links to boards available for buying:
http://www.provideo.com.tw/web/DVR%20Card_TW-310.htm
http://www.pr
On Friday 21 November 2014 03:11 AM, Mason wrote:
> On 19/11/2014 17:57, Victor Ascroft wrote:
>
>> On 11/19/2014 06:20 PM, Mason wrote:
>>
>>> Are there more recent technical references, as good as LDD3, that
>>> cover "modern" aspects of kernel development?
>> The LDD3 is one of the best there i
On 19/11/2014 17:57, Victor Ascroft wrote:
> On 11/19/2014 06:20 PM, Mason wrote:
>
>> Are there more recent technical references, as good as LDD3, that
>> cover "modern" aspects of kernel development?
>
> The LDD3 is one of the best there is. A fourth edition is supposed
> to come out sometime
On Wed, 19 Nov 2014 17:05:00 +0100
Mason wrote:
> Hello Andreas,
>
> On 19/11/2014 16:02, Andreas Färber wrote:
>
> > Am 19.11.2014 um 13:50 schrieb Mason:
> >
...
> > Since this appears to be about an ARM SoC according to your To list,
> > in general, you create a device tree binding, that bin
On Wed, Nov 19, 2014 at 9:35 PM, Mason wrote:
> Is there an exhaustive list of available buses (on the ARM platform)
> and an overview of when/where each one is appropriate?
Not sure if its mentioned that clearly anywhere. BUT bus is normally
bound by the way you need to access registers of a dev
On 11/19/2014 10:49 PM, Mason wrote:
> On 19/11/2014 17:57, Victor Ascroft wrote:
>
>> This actually depends on the kernel you are using. Do you have relatively
>> new kernel or an old one? Depending on that, either you will get that
>> information in a board file or else in the device tree in ar
On 19/11/2014 17:57, Victor Ascroft wrote:
This actually depends on the kernel you are using. Do you have relatively
new kernel or an old one? Depending on that, either you will get that
information in a board file or else in the device tree in arch/arm/boot/dts.
I'll reply more thoroughly lat
I'm finding the transition harder than I expected.
>
> I'm having a hard time finding good reference material to bring me up to
> speed on the ins
> and outs of driver development. Sure, I found Documentation/driver-model
> (eventually) but
> I'm still missing
Hello Andreas,
On 19/11/2014 16:02, Andreas Färber wrote:
Am 19.11.2014 um 13:50 schrieb Mason:
[...] I'm writing a driver for a temperature sensor, which is
supposed to work within the hwmon/lm-sensors framework.
The sensor's API consists of 3 memory-mapped registers, which are
accessible o
Hi,
Am 19.11.2014 um 13:50 schrieb Mason:
> [...] I'm writing a driver for a temperature sensor, which is
> supposed to work
> within the hwmon/lm-sensors framework.
>
> The sensor's API consists of 3 memory-mapped registers, which are
> accessible over the
> SoC's memory bus. [...]
>
> 1) Which
ing a hard time finding good reference material to bring me up to speed
on the ins
and outs of driver development. Sure, I found Documentation/driver-model
(eventually) but
I'm still missing the high-level overview that ties everything together, and
makes my
brain click and "get it"
On Fri, Sep 06, 2013 at 10:47:58AM +, Steve Twiss wrote:
> Is it possible to remove this driver from linux-next so these issues
> can be resolved by Dialog?
No, sorry. The regulator tree has already been merged into Linus' tree
for v3.12 so can't be changed now.
In any case the best approa
ernel.
>
> It is well understood that any early submission of our driver to the
> community (around v3.6) meant that this sort of external driver development
> could happen without any further input from Dialog. However, this driver:
>
> - is based on something that is a year ol
Could copy me the mfd.c file of da9063 in the lkml?
-Original Message-
From: Steve Twiss
Sent: 06 September 2013 11:48
To: Mark Brown; Philipp Zabel
Cc: Lee Jones; Samuel Ortiz; LKML
Subject: DA9063 driver development
Hello,
I am late into the discussion about the DA9063 driver because
earlier in https://lkml.org/lkml/2013/6/28/170 I was in
the process of getting this driver ready for submission to the kernel.
It is well understood that any early submission of our driver to the
community (around v3.6) meant that this sort of external driver development
could happen without
elli
- Original Message -
From: "Marek Vasut"
To: "Bastelli Carlo"
Cc: "Ned Forrester" ; "Fabio Estevam"
; ;
;
Sent: Saturday, August 25, 2012 1:44 PM
Subject: Re: SLAVE Side SPI kernel driver development
Dear Bastelli Carlo,
> In my applicati
;
> ; ;
>
> Sent: Friday, August 24, 2012 6:54 PM
> Subject: Re: SLAVE Side SPI kernel driver development
>
> On 08/24/2012 11:38 AM, Marek Vasut wrote:
> > Dear Fabio Estevam,
> >
> >> On Fri, Aug 24, 2012 at 11:57 AM, Bastelli Carlo (yahoo)
>
- Original Message -
From: "Ned Forrester"
To: "Marek Vasut"
Cc: "Fabio Estevam" ;
; "Bastelli Carlo (yahoo)"
; ;
Sent: Friday, August 24, 2012 6:54 PM
Subject: Re: SLAVE Side SPI kernel driver development
On 08/24/2012 11:38 AM, Marek Vasut wrote
On 08/24/2012 11:38 AM, Marek Vasut wrote:
> Dear Fabio Estevam,
>
>> On Fri, Aug 24, 2012 at 11:57 AM, Bastelli Carlo (yahoo)
>
> CCing SPI list
>
>> wrote:
>>> Hello, I'm Carlo, I have a difficult task at work, my boss asked me to
>>> develop
>>>
>>> a driver SPI slave side on embedded ARM p
Dear Fabio Estevam,
> On Fri, Aug 24, 2012 at 11:57 AM, Bastelli Carlo (yahoo)
CCing SPI list
> wrote:
> > Hello, I'm Carlo, I have a difficult task at work, my boss asked me to
> > develop
> >
> > a driver SPI slave side on embedded ARM processor running Linux.
> >
> > Precisely linux occur
On Fri, Aug 24, 2012 at 11:57 AM, Bastelli Carlo (yahoo)
wrote:
> Hello, I'm Carlo, I have a difficult task at work, my boss asked me to
> develop
> a driver SPI slave side on embedded ARM processor running Linux.
> Precisely linux occur on the SPI bus as a slave, not master as required
> by the
Hello, I'm Carlo, I have a difficult task at work, my boss asked me to
develop
a driver SPI slave side on embedded ARM processor running Linux.
Precisely linux occur on the SPI bus as a slave, not master as required
by the hierarchical structure of the current kernel. The new driver
will
rece
Hello, I'm Carlo, I have a difficult task at work, my boss asked me to
develop
a driver SPI slave side on embedded ARM processor running Linux.
Precisely linux occur on the SPI bus as a slave, not master as required
by the hierarchical structure of the current kernel. The new driver
will
rece
Hi!
> >What's so hard about submitting a 200 line patch to LKML?
>
> that's what i was wondering about ;D
> it's not the first time, that i see nice features not being submitted to lkml.
>
> anyway - pavel (thanks btw!) just pointed me to some param "mem=exactmap" :
>
> >I think functionality i
On 3/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
It seems, that BadRAM is not being maintained very actively and the original author
doesn`t seem to have the time pushing it into mainline, but i know it's actively being
used by more then just a handful of people. Unfortunately there is n
AM-2.6.19.1.patch
Sorry for being a little bit "noisy" here, but I think BadRAM is a
great feature and Linux could really benefit from that.
regards
Roland K.
Sysadmin
List: linux-kernel
Subject:Re: Free Linux Driver Development!
From: devzero () web ! de
Date:
/BadRAM-2.6.19.1.patch
>
> Sorry for being a little bit "noisy" here, but I think BadRAM is a great
feature and Linux could really benefit from that.
>
> regards
> Roland K.
> Sysadmin
>
>
> List: linux-kernel
> Subject:Re: Free Linux Driver Developm
Hi!
> > This kind of offer has _always_ been there for out-of-tree GPL drivers.
> > I have contacted many different groups and driver authors over the years
> > to offer my help in trying to get their code into the mainline kernel.
> >
> > Some take me up on the offer, others ignore it, and still
On Tue, 6 Feb 2007, Akemi Yagi wrote:
On Tue, 06 Feb 2007 19:07:50 +0530, Sunil Naidu wrote:
On 2/5/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
Wrong. I abandoned all fl
On Wed, Feb 07, 2007 at 08:12:05AM +0100, Miguel Ojeda wrote:
>
> As I'm not an expert in any kind of device, so I would like to join
> for any device which its type has not been assigned to any person yet
> (wild card?). Also, I would code for small LCDs.
Thanks, I've added you to the list.
I'l
On Wed, Feb 07, 2007 at 06:03:58AM -0800, Tejun Heo wrote:
> I can write ATA drivers for most hardware in a few days given 1.
> actually useful datasheet 2. hardware at hand 3. an ENGINEER to talk to
> when I get stuck. So, sign me up.
Thanks, I'll add you to the list.
> It will be nice to hav
Eric Sandeen wrote:
Jeff Garzik wrote:
Eric Sandeen wrote:
Jeff Garzik wrote:
Roland Dreier wrote:
And I seem to recall there's more SATA chipset documentation than Jeff
Garzik has time to implement support for.
I seriously doubt you can come up with even a single concrete example here.
Not
On Wed, Feb 07, 2007 at 07:03:26PM +0530, Sunil Naidu wrote:
> Yep, still floppies are useful. Example, when we buy a new device
> (driver) with a floppy (sometimes by manufacturer). Plus, from the
> customer (not user) POV, what's wrong in spending another $10 for a
> FDD in a typical $1000 PC? Ma
On 2/7/07, Akemi Yagi <[EMAIL PROTECTED]> wrote:
On Tue, 06 Feb 2007 19:07:50 +0530, Sunil Naidu wrote:
> On 2/5/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
>> On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
>> > On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
>>
>> Wron
> > > I have a Cisco USB webcam that supposedly conforms to the "USB Video
> > > Device Class", but nothing happens when I plug it into my Linux box.
> > > I assume the device class is specified as part of the USB spec...
> >
> > Are you sure? That spec just came out not so long ago and I hav
On 2/6/07, Greg KH <[EMAIL PROTECTED]> wrote:
On Tue, Feb 06, 2007 at 12:29:03PM +0400, Manu Abraham wrote:
> On 2/6/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >On Sun, Feb 04, 2007 at 07:59:47PM +0100, Pierre Ossman wrote:
> >> Hi Greg,
> >>
> >> Although I am a bit of a cynic, I really hope that
> From: Akemi Yagi
> Newsgroups: gmane.linux.kernel
> Subject: Re: Free Linux Driver Development!
> Date: Tue, 06 Feb 2007 13:14:44 -0800
[]
>> I don't think time has come for that yet, still millions of people do use
>> Floppy on Linux ;-)
>
> So, I am not
On Tue, 06 Feb 2007 19:07:50 +0530, Sunil Naidu wrote:
> On 2/5/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
>> On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
>> > On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
>>
>> Wrong. I abandoned all floppy drives some years ago. I'
On Tue, Feb 06, 2007 at 12:29:03PM +0400, Manu Abraham wrote:
> On 2/6/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >On Sun, Feb 04, 2007 at 07:59:47PM +0100, Pierre Ossman wrote:
> >> Hi Greg,
> >>
> >> Although I am a bit of a cynic, I really hope that this endeavor works
> >> the way you hope.
> >>
On Tue, Feb 06, 2007 at 07:05:10PM +0530, Sunil Naidu wrote:
> >Just let me know what types of devices you are interested in working on.
>
> I would love to work on PC as well as Embedded stuff (Power, Intel, and
> ARM).
> Devices types - Audio/Video (this needs special attention for the
> Linux
On Tuesday 06 February 2007 11:30, Gene Heskett wrote:
>On Tuesday 06 February 2007 08:37, Sunil Naidu wrote:
>>On 2/5/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
>>> On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
>>> > On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
>>>
>
On Tuesday 06 February 2007 08:37, Sunil Naidu wrote:
>On 2/5/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
>> On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
>> > On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
>>
>> Wrong. I abandoned all floppy drives some years ago. I'd a
On Tue, Feb 06, 2007 at 10:12:04AM -0500, Bill Davidsen wrote:
> Stefan Seyfried wrote:
> >On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
> >>On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
> >>>What? Throw a fresh-faced newbie instantly into the tar-pit of despair
> >>>that
Stefan Seyfried wrote:
On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
What? Throw a fresh-faced newbie instantly into the tar-pit of despair
that floppy.c is? Do you want everyone just to run screaming from
kernel develo
On Tue, Feb 06, 2007 at 07:07:50PM +0530, Sunil Naidu wrote:
> On 2/5/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> > On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
> > > On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
> >
> > Wrong. I abandoned all floppy drives some
On 2/5/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
> On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
Wrong. I abandoned all floppy drives some years ago. I'd actually
vote for removing the floppy driver from the kernel comp
> On 2/4/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >
> >Just let me know if you are interested in participating, and what types
> >of devices you wish to write drivers for (USB, PCI, network, etc.)
Yep, would love to dive into this oceanin available mode ;-)
> I would like to participate; h
On 2/6/07, Greg KH <[EMAIL PROTECTED]> wrote:
On Sun, Feb 04, 2007 at 07:59:47PM +0100, Pierre Ossman wrote:
> Hi Greg,
>
> Although I am a bit of a cynic, I really hope that this endeavor works
> the way you hope.
>
> I'd also like to offer my services to this quest of yours. If you get
> any SD
On Sun, Feb 04, 2007 at 07:59:47PM +0100, Pierre Ossman wrote:
> Hi Greg,
>
> Although I am a bit of a cynic, I really hope that this endeavor works
> the way you hope.
>
> I'd also like to offer my services to this quest of yours. If you get
> any SD, MMC or SDIO requests, feel free to pass them
On Mon, Feb 05, 2007 at 04:24:21PM +0100, Jiri Slaby wrote:
> Greg KH napsal(a):
> >On Sun, Feb 04, 2007 at 08:08:32PM +0100, Miguel Ojeda wrote:
> >>On 2/4/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >>>Just let me know if you are interested in participating, and what types
> >>>of devices you wish t
Greg KH napsal(a):
On Sun, Feb 04, 2007 at 08:08:32PM +0100, Miguel Ojeda wrote:
On 2/4/07, Greg KH <[EMAIL PROTECTED]> wrote:
Just let me know if you are interested in participating, and what types
of devices you wish to write drivers for (USB, PCI, network, etc.)
I would like to participate;
On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
> On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
> > What? Throw a fresh-faced newbie instantly into the tar-pit of despair
> > that floppy.c is? Do you want everyone just to run screaming from
> > kernel development never to
On Sun, Feb 04, 2007 at 08:08:32PM +0100, Miguel Ojeda wrote:
> On 2/4/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >
> >Just let me know if you are interested in participating, and what types
> >of devices you wish to write drivers for (USB, PCI, network, etc.)
> >
> >thanks,
> >
> >greg k-h
> >
>
>
> From: devzero web.de
> Newsgroups: gmane.linux.kernel
> Subject: Re: Free Linux Driver Development!
> Date: Sun, 04 Feb 2007 22:37:33 +0100
> Organization: http://freemail.web.de/
> Archived-At: <http://permalink.gmane.org/gmane.linux.kernel/489586>
> First off, compl
First off, compliments to this announcement, I liked it very much!
Some comment regarding those "volunteers, waiting to get some real work" :)
> > OK, but why isn't your army of volunteers fixing them?
> They don't know about them, or they don't have the hardware to test?
> Seriously, let the ke
Greg KH <[EMAIL PROTECTED]> writes:
> Or perhaps your device just needs to add some flow control to it :)
Physical processes are hard to pause. :-)
But yes, adding a 16kByte FIFO before the FT245 would have made life
so much easier for me, but unfortunately the thing that drives the
hardware cho
Jan Engelhardt wrote:
On Jan 31 2007 08:34, David Hollis wrote:
Conversely, I've seen many cases of drivers that are developed by the
community, but kept out-of-kernel forever due to various reasons. Some
of them are due to the code quality and the developers not accepting the
feedback to get t
On 2/4/07, Greg KH <[EMAIL PROTECTED]> wrote:
Just let me know if you are interested in participating, and what types
of devices you wish to write drivers for (USB, PCI, network, etc.)
thanks,
greg k-h
I would like to participate; however, for people who is not at USA
(say, Europe), are the
Hi Greg,
Although I am a bit of a cynic, I really hope that this endeavor works
the way you hope.
I'd also like to offer my services to this quest of yours. If you get
any SD, MMC or SDIO requests, feel free to pass them along to me. I am
not a big fan of debug-by-email though, so I'd prefer vend
On Sun, Feb 04, 2007 at 03:04:58AM -0800, Parav Pandit wrote:
> Hi,
>
> So how can an individual like me having ardor, contribute in Free
> driver development? What is the eligibility criteria and process for
> contributing in this activity?
>
> In brief, I come with bac
On Sun, Feb 04, 2007 at 02:29:13PM +0100, Christer Weinigel wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
>
> > Why would a userspace driver not work out for this. We already can
> > saturate the USB bus with a userspace program
>
> That is unfortunately not quite true. I have a (unfortunately
>
Greg KH <[EMAIL PROTECTED]> writes:
> Why would a userspace driver not work out for this. We already can
> saturate the USB bus with a userspace program
That is unfortunately not quite true. I have a (unfortunately
proprietary) driver for a USB device that simply cannot be implemented
in usersp
On Sunday 04 February 2007 07:26, Larry Finger wrote:
> What is true is that none of the OFDM rates work
> because of some unknown bug, probably in initialization. As a result, we are
> limited to a maximum
> data rate of 11Mbs, but it is still running in 802.11g mode!
That's also not true for m
On Thu, Feb 01, 2007 at 09:45:45PM EST, Lennart Sorensen wrote:
>On Thu, Feb 01, 2007 at 02:59:03PM +0100, Erik Mouw wrote:
>> I can't remember that kind of corruption ever being reported to the
>> bcm43xx-dev mailing list.
I came into this discussion late as I only read LKML in summary form, but
Pekka Enberg wrote:
On 2/2/07, Jan Dittmer <[EMAIL PROTECTED]> wrote:
Pekka, it would be better if you could sort out most of the
basic issues with lirc directly with the developers of lirc
and then prepare a complete patch series and post that to
lkml. Incrementally adding one driver after anot
On 2/2/07, Jan Dittmer <[EMAIL PROTECTED]> wrote:
Pekka, it would be better if you could sort out most of the
basic issues with lirc directly with the developers of lirc
and then prepare a complete patch series and post that to
lkml. Incrementally adding one driver after another. Posting
patches
Pekka J Enberg wrote:
From: Pekka Enberg <[EMAIL PROTECTED]>
On 02 Feb 2007 05:54:00 +0100, Christoph Bartelmus <[EMAIL PROTECTED]> wrote:
I just made clear that I don't have the time to do the merging of LIRC
drivers to the kernel myself. In fact a lot of work still needs to be
done before LIR
On 2/2/07, Pekka J Enberg <[EMAIL PROTECTED]> wrote:
From: Pekka Enberg <[EMAIL PROTECTED]>
[...]
drivers/lirc_atiusb/lirc_atiusb.c | 102 -
^^
I may be mistaken, but the lirc_atiusb module looks redondant with
the driver alre
On Wed, 31 Jan 2007 21:20:06 +0100 Greg KH wrote:
> On Wed, Jan 31, 2007 at 02:06:32PM +0100, Nicolas Mailhot wrote:
>> I'd really love if the same offer was extended to GPL out-of-tree
>> driver trees.
>
> This kind of offer has _always_ been there for out-of-tree GPL
> drivers. I have contacted
On Thu, Feb 01, 2007 at 09:45:06AM -0500, Lennart Sorensen wrote:
> On Thu, Feb 01, 2007 at 02:59:03PM +0100, Erik Mouw wrote:
> > I can't remember that kind of corruption ever being reported to the
> > bcm43xx-dev mailing list.
>
> Well I assumed it messed up the eeprom settings, since we had to
On 2/1/07, Lennart Sorensen <[EMAIL PROTECTED]> wrote:
Sometimes I might be. At least on the days I have to deal with problems
in Windows (it's not even my machine, so I don't get to pick what it
runs all the time. :) I haven't had particularly much luck getting a
stable wireless going on linux
Alan <[EMAIL PROTECTED]> writes:
>> 3. Vendor driver is rather close to the generic one being in the kernel,
>>so maybe it's better to improve generic one instead of adding yet
>>another driver to the tree.
>
> Firstly can you post a patch which adds the relevant identifiers to the
> curren
On Thu, Feb 01, 2007 at 02:12:22PM +0100, Bartlomiej Zolnierkiewicz wrote:
> On 31 Jan 2007 11:08:14 +0100, Andi Kleen <[EMAIL PROTECTED]> wrote:
> >Greg KH <[EMAIL PROTECTED]> writes:
> >>
> >> What? Throw a fresh-faced newbie instantly into the tar-pit of despair
> >> that floppy.c is? Do you w
On Thu, Feb 01, 2007 at 04:46:38PM +0100, Michael Buesch wrote:
> Nah, why do you think it will screw up the eeprom?
> Did you try to completely power off the machine before rebooting
> into windows?
No at the time I don't think I powered it off, and I suspect that is
probably what went wrong. Th
On Tuesday 30 January 2007 23:23, Lennart Sorensen wrote:
> On Tue, Jan 30, 2007 at 05:12:31PM -0500, Jeff Garzik wrote:
> > You mean the bcm43xx wireless driver that's been upstream for months?
>
> And seems to do 802.11b only and screw up the eeprom settings so that
> the windows driver gets con
On Thu, Feb 01, 2007 at 02:59:03PM +0100, Erik Mouw wrote:
> I can't remember that kind of corruption ever being reported to the
> bcm43xx-dev mailing list.
Well I assumed it messed up the eeprom settings, since we had to go into
the advanced driver settings and change it from 802.11b only back to
> 3. Vendor driver is rather close to the generic one being in the kernel,
>so maybe it's better to improve generic one instead of adding yet
>another driver to the tree.
Firstly can you post a patch which adds the relevant identifiers to the
current pcmcia serial driver so that 115,200 wo
Greg KH <[EMAIL PROTECTED]> writes:
> On Wed, Jan 31, 2007 at 08:41:03PM +0300, Sergei Organov wrote:
>> Greg KH <[EMAIL PROTECTED]> writes:
>> [...]
>> >> And there are plenty of documented devices that no one cares enough
>> >> about to submit a driver for.
>> >
>> > Any specific examples? I ha
On Tue, Jan 30, 2007 at 05:23:44PM -0500, Lennart Sorensen wrote:
> On Tue, Jan 30, 2007 at 05:12:31PM -0500, Jeff Garzik wrote:
> > You mean the bcm43xx wireless driver that's been upstream for months?
>
> And seems to do 802.11b only and screw up the eeprom settings so that
> the windows driver
On 01/02/07, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
On 31 Jan 2007 11:08:14 +0100, Andi Kleen <[EMAIL PROTECTED]> wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
> >
> > What? Throw a fresh-faced newbie instantly into the tar-pit of despair
> > that floppy.c is? Do you want everyone
On 31 Jan 2007 11:08:14 +0100, Andi Kleen <[EMAIL PROTECTED]> wrote:
Greg KH <[EMAIL PROTECTED]> writes:
>
> What? Throw a fresh-faced newbie instantly into the tar-pit of despair
> that floppy.c is? Do you want everyone just to run screaming from
> kernel development never to be seen again?
On Jan 31 2007 18:59, Lee Revell wrote:
> On 1/31/07, Theodore Tso <[EMAIL PROTECTED]> wrote:
>>
>> More specifically, Dave said that it "seemed rude" to just take the
>> driver and send updates, but maybe the best way of dealing with
>> out-of-tree drivers like lirc is to treat the out-of-tree dr
Lee Revell wrote:
On 1/31/07, Mark Lord <[EMAIL PROTECTED]> wrote:
I believe a BIG reason why lots of open-source drivers are out-of-tree
right now, is because lkml is perceived as being wayy too fussy
and petty about 80-column lines, brackets, etc.. for new code.
It's just not worth the ef
On 2/1/07, Nicolas Mailhot <[EMAIL PROTECTED]> wrote:
Not all of them.
It seems it's kosher to rewrite a corp GPL driver but not a "community" one.
As I said, Greg didn't say it was rude to write a new driver without consulting
the author of an existing driver.. corp *or* community.. so who sai
Le Jeu 1 février 2007 10:03, Trent Waddington a écrit :
> On 2/1/07, Nicolas Mailhot <[EMAIL PROTECTED]> wrote:
>> Well, reengineering nvidia/ati DRM is rude to ati/nvidia, so was
>> creating
>> tigon3, so was rewriting from scratch the GPL drivers some ATA vendors
>> published in the past, so was
On 2/1/07, Nicolas Mailhot <[EMAIL PROTECTED]> wrote:
Well, reengineering nvidia/ati DRM is rude to ati/nvidia, so was creating
tigon3, so was rewriting from scratch the GPL drivers some ATA vendors
published in the past, so was spurning the SATA/SAS stack adaptec
offered...
It is rude, but the
Le Jeu 1 février 2007 00:44, Greg KH a écrit :
> On Wed, Jan 31, 2007 at 06:00:15PM -0500, Theodore Tso wrote:
>> More specifically, Dave said that it "seemed rude" to just take the
>> driver and send updates, but maybe the best way of dealing with
>> out-of-tree drivers like lirc is to treat the
On Wed, Jan 31, 2007 at 01:37:58PM -0500, Bob Copeland wrote:
> >Putting the "codingstyle" control aside, often it's because things look
> >too hackish.
>
> Also sometimes the authors know it's hackish, or just don't expect it
> to be generally useful to the world. I happen to own an out-of-tree
On Wed, Jan 31, 2007 at 10:15:20PM +0100, Nicolas Mailhot wrote:
> Le mercredi 31 janvier 2007 ?? 12:12 -0800, Greg KH a ??crit :
> > On Wed, Jan 31, 2007 at 02:06:32PM +0100, Nicolas Mailhot wrote:
>
> [Reordering for the sake of argument]
>
> > > There are many out-of-tree drivers (ivtv, lirc,
On Wed, Jan 31, 2007 at 08:41:03PM +0300, Sergei Organov wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
> [...]
> >> And there are plenty of documented devices that no one cares enough
> >> about to submit a driver for.
> >
> > Any specific examples? I have a long list of people who wish to write
>
On Thu, Feb 01, 2007 at 10:07:53AM +1000, Trent Waddington wrote:
> On 2/1/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >No, I'm going by Linus's rule here, if a person doesn't want their code
> >in the kernel tree, then I'm not going to forcefully put it there.
> >That's just being rude.
>
> Makes se
On 1/31/07, Mark Lord <[EMAIL PROTECTED]> wrote:
Randy Dunlap wrote:
> On Wed, 31 Jan 2007 18:00:15 -0500 Theodore Tso wrote:
..
>> More specifically, Dave said that it "seemed rude" to just take the
>> driver and send updates, but maybe the best way of dealing with
>> out-of-tree drivers like li
Randy Dunlap wrote:
On Wed, 31 Jan 2007 18:00:15 -0500 Theodore Tso wrote:
..
More specifically, Dave said that it "seemed rude" to just take the
driver and send updates, but maybe the best way of dealing with
out-of-tree drivers like lirc is to treat the out-of-tree drivers as a
kind of spec r
On 2/1/07, Greg KH <[EMAIL PROTECTED]> wrote:
No, I'm going by Linus's rule here, if a person doesn't want their code
in the kernel tree, then I'm not going to forcefully put it there.
That's just being rude.
Makes sense when you put it that way. However, perhaps an offer to
take over the main
On 1/31/07, Theodore Tso <[EMAIL PROTECTED]> wrote:
More specifically, Dave said that it "seemed rude" to just take the
driver and send updates, but maybe the best way of dealing with
out-of-tree drivers like lirc is to treat the out-of-tree drivers as a
kind of spec release, and just have someon
1 - 100 of 228 matches
Mail list logo
