Slashdot Mirror


Upping The Softmodem Code Bounty -- To $20,000

Alex Pilosov writes: "I've announced a bounty for completion of softmodem code (20k$) on linmodems-discuss list. If this is successfully completed, we'll have a completely universal driver for any kind of winmodem without any proprietary code which result in all sorts of kernel version problems." Here's the full text of the announcement and conditions.

13 of 234 comments (clear)

  1. Reasons why this would be interesting! by denisb · · Score: 5, Insightful

    Can't people figure out the following reasons for such a project being interesting ?

    - Low cost internet station for places out of reach of xDSL / cable modem connections.
    - Viable internet connection for legacy hardware / second hand hardware
    - Excellent solution for development countries where xDSL is faar away yet.

    The keywords here are LOW and COST.. Did you ever consider that Linux and second hand hardware might be the ultimate combination for places where they don't have as much cash as yourselves ?

    d9s

    --
    life+universe+everything=42
  2. Re:high price for a modem by Kraft · · Score: 5, Insightful

    think laptops...

    I have a thinkpad t21, and from what I have read, one of the common linux problems with this laptop is bad modem support. As I use this machine on the road from time to time, I want that modem to work (hotels, friends house etc.) and if it doesn't it will be a deterrent to install linux.

    I do think you are right in suposing that many linux fans are early adopters, but what I find interesting is the possibility of more "regular" users switching to linux, because of proper hardware support and thus: ease of use.

    --

    -Kraft
    Live and let live
  3. Re:restrictions? by krokodil · · Score: 5, Insightful

    You MUST have background in signal processing

    Dear Mr. Torvalds,

    We could not permit your so-called "operating system" to use GNU license because you do not have proven experience in the operating system design and your background is not sufficient. In order to satisfy our customers,
    and maintain high project code quiality, we accept contributions only from candidates who have experience in the particular area and passed interview with some of our managers.

    (signed)
    Free Software Foundaiton

  4. Patents on modem algorithms? by dido · · Score: 4, Insightful

    I'm just wondering if perhaps someone has patented the algorithms used to drive these soft modems. A Free Software implementation of a soft modem driver will thus be in violation of the patent then. As far as I can tell the ITU, the standards body that defines these modem standards, allows what the W3C calls RAND licensing, as they state in patent policy (excerpt):

    2 If an ITU-T Recommendation is developed and such information as referred to in paragraph 1 [patents and other intellectual property claims], three different situations may arise:

    2.1 The patent holder waives his rights; hence, the Recommendation is freely accessible to everybody, subject to no particular conditions, no royalties are due, etc.

    2.2 The patent holder is not prepared to waive his rights but would be willing to negotiate licenses with other parties on a non-discriminatory basis on reasonable terms and conditions. Such negotiations are left to the parties concerned and are performed outside the ITU-T. [emphasis mine]

    2.3 The patent holder is not willing to comply with the provisions of either paragraph 2.1 or paragraph 2.2; in such case, no Recommendation can be established.

    It's paragraph 2.2 that worries me. If any patents exist on the modem standards implemented by soft modems that are thus RAND-licensable, any GPL implementation is impossible. I believe some of the compression algorithms used in some of the modem standards are already known to be patented, such as the infamous LZW compression algorithm held by Unisys that has caused the huge flap over GIF's a couple of years back.

    --
    Qu'on me donne six lignes écrites de la main du plus honnête homme, j'y trouverai de quoi le faire pendre.
  5. Winmodem hardware compatibility by Novus · · Score: 3, Insightful
    If this is successfully completed, we'll have a completely universal driver for any kind of winmodem without any proprietary code which result in all sorts of kernel version problems.

    As far as I can tell, this project doesn't solve the problem of winmodem manufacturers not releasing hardware specs. In other words, you'd have a driver that can tell a DAC/ADC driver what to squirt down the line and work out what the stuff that comes back means, but you still wouldn't be able to use the actual winmodem; you'd have to use a DAC/ADC for which you have drivers. This means either buying a supported modem or a separate DAC, or trying to figure out how to drive the winmodem's DAC and ADC directly.

    Of course, persuading manufacturers to release one or two port adresses and a little info on how to use them may be easier than getting them to release full Linux drivers or complete DSP specs. Likewise, working out how to access the DAC/ADC on a winmodem is probably easier than trying to figure out its DSP (although the DAC/ADC may be only accessible to the DSP, which may make things hairy).

  6. Re:Bountys - a great Way to fund development of OS by ab315 · · Score: 3, Insightful
    Bounties are a TERRIBLE way to fund development of software.

    No serious developer is going to go after a bounty, because you only have a 1/N chance of getting the prize if there are N other contenders. The person who finishes first is going to be the one who cuts the most corners and spends the least amount of time on design and documentation, so you'll end up rewarding the person who can produces the crappiest software to a minimum standard faster than anyone else!

    The competitive aspect also makes people keep their work secret, preventing peer review and feedback.

    Sheesh, if someone has $20,000 to spend on software development they should just HIRE a skilled person who will get the job done properly. It's not like there's a shortage of skilled software developers at the moment! They don't even have to be a free software developer because if you're hiring them you call the shots and choose whatever license you want.

  7. Licensing too. by Karpe · · Score: 3, Insightful

    Not only you are right, but also any communication equipment connected to the phone network must be licensed by the local communications agency. This happens in many countries. Most of them will never bother to go after people connecting linmodems on the phone network, but some countries are very rigid in this control. This licensing, or approvement, must apply to the communication equipment as a whole. You can't license only the hardware part of software modems, since many times is the software that will decide the line levels to be used. (In Lucent winmodems, these levels are selected via AT commands, when you select the country you are in. This is done via software). This process is necessary to avoid people connecting devices to the phone network that could ruin the network.

    So, in short, even if we don't worry with the patent issues of v.xx, we still have to worry on licensing the linmodem software, but since free software can always be modified, there will always have a non-approved version of it, which can cause legal problems.

  8. Who pays the lawyers? by Florian+Weimer · · Score: 3, Insightful

    I doubt you can implement those ITU standards without infringing on a couple of patents (at least a few companies will claim infringement as soon as you publish the code).

    If you have to pay the lawyers from your $20,000, this doesn't appear to be a fair deal.

  9. Screw Microsoft and promote the uptake of Linux by pubjames · · Score: 3, Insightful


    I've often thought that it is in many companies interests to find ways to screw over Microsoft, even in ways that are apparently not directly beneficial to them. I've always thought that this is probably one of the main motivating factors behind openoffice.org - it might not generate much profit for Sun, but it has the potential to kick Microsoft where it hurts, as the cream of their profits come from Office. Similarly with IBM's support and nurturing of SUSE, Mandrake and Redhat.

    Of course there many be companies that have identified places they want to kick Microsoft but don't want to do it publicly. Take Intel for instance - despite their long-term relationship with Microsoft I'm sure they would prefer to drive sales of their processors by releasing open source developers toolkits that exploit new features they add to their processors. So its in their interest to promote the uptake of Linux, but without risking the wrath of Bill. This is one way they could do it - give bounties via a third party for development that they see as strategic for the wider uptake of Linux.

    And not just Intel - there are many other companies that have the motivation to do this type of thing but don't want attention drawn their way.

  10. How do we know that this is genuine? by HuskyDog · · Score: 5, Insightful
    I don't want to be rude, but how do we know that this guy will produce the money? Can anyone we trust vouch for him?

    Perhaps if he placed a deposit with some trusted third party (Mad Dog, Eric Raymond etc) people might be happier to devote the time.

  11. Re:Bounty won't matter much. by pjrc · · Score: 5, Insightful
    A couple years ago I designed a product with an embedded modem (H8800-1 at this page). I used a rockwell chip and associated components, which is a hardware modem.

    Device is the keyword here, and the device (winmodem) has already been certified. The software driving the device doesn't need certification.

    This may not true. When we tested the H8800-1 for FCC part 68 compliance, the test was for the whole system. We had to provide ways for them to access the modem to test both originate and answer modes (though the H8800-1 only answers and never originates). We had to do this, despite the fact that the signals were all generated by the Rockwell chip.

    However, the majority of the trouble with FCC part 68 is the surge tests. The basic idea behind these tests is to apply a massive surge on the line which is certain to destroy the modem. The modem is required to fail in a manner where it does not conduct, so it looks like it's on-hook (not in use) to the phone network. This is purely a function of the hardware. The lab we sent the prototypes to did many other tests, but they were all pretty easy to pass (using the rockwell chip).

    Reading through these regularity requirement documents is a mind-numbing experience (if you can stay awake). If you're feeling maschoistic, here is the page for requesting the Part 68 technical requirements. If anyone takes the time to actually read and make some sense out of this stuff, please post your informed opinions. Part 68 applies only to the US, so repeat for whatever other countries you're interested in...

  12. Why require Compression?? by A+Commentor · · Score: 3, Insightful

    V.42bis and MNP5 should be optional.

    As long as the software is able to properly negotiate no compression with the other modem, requiring Compression adds a substanial amount of work that can be post-poned or have another person work on it.

    --

    Looking for any old 8-bit Heathkit/Zenith software/hardware - http://heathkit.garlanger.com

  13. Re:problems by pubjames · · Score: 4, Insightful

    M$ has convinced many hardware makers that M$'s method of code breaking and bloat are the only way to drive new hardware sales.

    I think this probably underestimates the sophistication of thinking at hardware manufacturers, and the diversity of the market.

    Take, for instance, the 3D computer graphics sector. I am sure Intel was very pleased when Microsoft started to make a big drive to get NT used by companies in the 3D graphics production/rendering market, because they regularly buy lots of boxes. However, I bet they are even happier now that NT/Windows is no longer seen as attractive in this sector, and everyone is moving to Linux. Why? Because now they can add features to their chips that make them more attractive to this sector, and release the code as Open Source to stimulate need and uptake. They tried to do something similar before with Windows, but MS firmly stamped on their efforts.