mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Duncan Sands <baldrick@free.fr>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Grzegorz Kulewski <kangur@polcom.net>,
	Giampaolo Tomassoni <g.tomassoni@libero.it>,
	linux-kernel@vger.kernel.org,
	linux-atm-general@lists.sourceforge.net
Subject: Re: [ATMSAR] Request for review - update #1
Date: Mon, 5 Sep 2005 17:04:44 +0200	[thread overview]
Message-ID: <200509051704.44315.baldrick@free.fr> (raw)
In-Reply-To: <200509041754.54995.s0348365@sms.ed.ac.uk>

Hi Alistair,

> > The instalation is currently (with firmware loader instead of modem_run)
> > very simple: USE="atm" emerge ppp, download firmware and place it in
> > /lib/firmware, compile the kernel with speedtch support.
> 
> Compared to "place the firmware in /lib/firmware" on many other distros, this 
> sounds like a lot of work! The kernel speedtch provides no advantages to its 
> userspace alternative.

historically the main problem with using the kernel driver was getting hold of
an ATM aware pppd.  The step "USE="atm" emerge ppp" looks like gentoos way of
installing such a pppd.  Nowadays several major distributions ship with an
ATM aware pppd, so if you are using one there is nothing to be done.  Likewise,
most distributions ship a kernel with speedtch support.  So if you're using
such a distribution all you have to do to use the kernel driver is
"place the firmware in /lib/firmware".

On the other hand, it is misleading to say that with the user mode driver
all you have to do is place the firmware in /lib/firmware.  That's only
true if your distribution (eg: Mandrake) explicitly supports the user mode
driver and has pre-installed and configured it for you.  If you don't have
such a distribution then setting up the user mode driver, while not difficult,
does require some work.

> > I tried to use userspace driver some time ago but it wasn't working for me
> > so I gave up. I was using modem_run with kernel driver for long time to
> > load the firmware but there were many problems with it too (nearly every
> > kernel or modem_run upgrade was breaking something, modem_run was hanging
> > in D state in most unapropriate moments and so on).
> 
> This is not the case any longer.

I'm the one who fixed most of those problems by the way.

> > Now I am using pure kernel driver and firmware loader and it works 100%
> > ok. There were no problems with it for long time. And I don't even want to
> > look at this userspace driver again.
> 
> Conversely people (including myself) found the kernel implementation to be 
> buggy, and when userspace breaks, you can simply restart it.. when the kernel 
> breaks, you have to reboot.

Tell me what problems you've been seeing and I will try to fix them.

All the best,

Duncan.

  parent reply	other threads:[~2005-09-05 15:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-04 11:05 Giampaolo Tomassoni
2005-09-04 12:00 ` [Linux-ATM-General] " Francois Romieu
2005-09-04 13:13   ` R: " Giampaolo Tomassoni
2005-09-04 15:32     ` Francois Romieu
2005-09-04 18:44       ` R: " Giampaolo Tomassoni
2005-09-04 19:11         ` matthieu castet
2005-09-04 19:33           ` R: " Giampaolo Tomassoni
2005-09-04 19:42           ` Giampaolo Tomassoni
2005-09-05  6:05     ` Zoran Stojsavljevic
2005-09-05  6:21       ` R: " Giampaolo Tomassoni
2005-09-04 16:20 ` Alistair John Strachan
2005-09-04 16:41   ` Grzegorz Kulewski
2005-09-04 16:54     ` Alistair John Strachan
2005-09-04 17:22       ` Grzegorz Kulewski
2005-09-05 15:04       ` Duncan Sands [this message]
2005-09-04 18:36   ` R: " Giampaolo Tomassoni
2005-09-04 18:51     ` Alistair John Strachan
2005-09-05  9:36   ` David Woodhouse
2005-09-05 13:52     ` Alistair John Strachan
2005-09-05 13:56       ` David Woodhouse
2005-09-05 14:18         ` Alistair John Strachan
2005-09-05 14:32           ` David Woodhouse
2005-09-05 14:46   ` Duncan Sands
2005-09-04 16:55 ` Jiri Slaby

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200509051704.44315.baldrick@free.fr \
    --to=baldrick@free.fr \
    --cc=g.tomassoni@libero.it \
    --cc=kangur@polcom.net \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®