lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 6 Nov 2014 13:47:11 +0100
From:	Pavel Machek <pavel@....cz>
To:	Sebastian Reichel <sre@...nel.org>
Cc:	Pali Rohár <pali.rohar@...il.com>,
	kernel list <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	linux-omap@...r.kernel.org, tony@...mide.com, khilman@...nel.org,
	aaro.koskinen@....fi, freemangordon@....bg
Subject: Re: N900 modem support in 3.18-rc1

Hi!

> On Wed, Nov 05, 2014 at 11:03:59PM +0100, Pavel Machek wrote:
> > > Maybe you need to enable modem?
> > > 
> > > This is n900 init sequence from script: nokia-n900-configs.sh
> > 
> > From the dts, it looks like this should somehow work without this.
> 
> Right :) The n900-modem driver will take care of this if the "pm"
> parameter is set to 1 (which should be the default).

I actually had pm=0 on the command line, but I removed it now, and no
change:

root@...0:~# find /sys/bus/hsi/devices/n900-modem/
/sys/bus/hsi/devices/n900-modem/
/sys/bus/hsi/devices/n900-modem/power
/sys/bus/hsi/devices/n900-modem/power/control
/sys/bus/hsi/devices/n900-modem/power/runtime_active_time
/sys/bus/hsi/devices/n900-modem/power/autosuspend_delay_ms
/sys/bus/hsi/devices/n900-modem/power/runtime_status
/sys/bus/hsi/devices/n900-modem/power/runtime_suspended_time
/sys/bus/hsi/devices/n900-modem/modalias
/sys/bus/hsi/devices/n900-modem/driver
/sys/bus/hsi/devices/n900-modem/subsystem
/sys/bus/hsi/devices/n900-modem/uevent
root@...0:~# cat /proc/cmdline 
root=/dev/nfs nfsroot=192.168.1.6:/srv/nfs/n900 rw
ip=192.168.1.8::192.168.1.6:255.255.255.192::usb0:  no-omap-wd
no-ext-wd console=tty0
root@...0:~# 

Let me try with explicit =1. .. aha, that helps. Thanks!

Do you have an example client that can talk to ofonod?

What is needed to get voice calls to work?

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ