Mark Hindley | 1 Dec 2006 14:30
Picon

Parport data not tristated after use

Hi,

I am trying to use a stk200 type dongle to programme an AVR uC using
avrdude through ppdev. Programming works fine, but after releasing the port
the data lines stay low. This means the 79hc buffer in the dongle is not
disconnected and the uC does not reset. I have to manually disconnect
the cable, which negates the reason for having a buffered dongle in the
first place!

Could I have some advice on why the data lines are staying low, surely
they should become high-Z after release?

I don't think anything is trying to use the port (I have only just
enabled ppdev in my .config)

Hardare is Acer Apsire 1350. Kernel 2.6.18,
parport, parport_pc and ppdev are all modular.
I have tried module params, but they seem to be ignored (PnPBIOS
override?)

On load the drivers report:

Dec  1 12:35:37 mercury kernel: pnp: match found with the PnP device
'00:09' and the driver 'parport_pc'
Dec  1 12:35:37 mercury kernel: parport: PnPBIOS parport detected.
Dec  1 12:35:37 mercury kernel: parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]

As I start progamming I get:

Dec  1 12:35:37 mercury kernel: pnp: the driver 'parport_pc' has been registered
(Continue reading)

Mark Hindley | 1 Dec 2006 20:02
Picon

Parport data not tristated after use

I have compiled the  modules with DEBUG_PARPORT. The log files are
below. I hope that helps.

Thanks

Mark

Dec  1 18:26:19 mercury kernel: pnp: the driver 'parport_pc' has been registered
Dec  1 18:26:19 mercury kernel: pnp: match found with the PnP device '00:09' and the driver 'parport_pc'
Dec  1 18:26:19 mercury kernel: pnp: Res cnt 3
Dec  1 18:26:19 mercury kernel: pnp: res cnt 3
Dec  1 18:26:19 mercury kernel: pnp: Encode io
Dec  1 18:26:19 mercury kernel: pnp: Encode io
Dec  1 18:26:19 mercury kernel: pnp: Encode irq
Dec  1 18:26:19 mercury kernel: pnp: Device 00:09 activated.
Dec  1 18:26:19 mercury kernel: parport: PnPBIOS parport detected.
Dec  1 18:26:19 mercury kernel: __parport_pc_frob_control(20,20): 0c -> 2c
Dec  1 18:26:19 mercury kernel: parport_pc_write_data(c9d13800,0x55)
Dec  1 18:26:19 mercury kernel: parport_pc_read_data(c9d13800) = 0xff
Dec  1 18:26:19 mercury kernel: parport_pc_write_data(c9d13800,0xaa)
Dec  1 18:26:19 mercury kernel: parport_pc_read_data(c9d13800) = 0xff
Dec  1 18:26:19 mercury kernel: __parport_pc_frob_control(20,00): 2c -> 0c
Dec  1 18:26:19 mercury kernel: parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
Dec  1 18:26:19 mercury kernel: parport_pc_write_data(c9d13800,0x00)
Dec  1 18:26:19 mercury kernel: __parport_pc_frob_control(20,00): 0c -> 0c
Dec  1 18:26:19 mercury kernel: parport0: cpp_daisy: aa5500ff(38)
Dec  1 18:26:19 mercury kernel: parport0: assign_addrs: aa5500ff(38)
Dec  1 18:26:19 mercury kernel: parport0: Peripheral not IEEE1284 compliant (0xDE)
Dec  1 18:26:19 mercury kernel: parport0: cpp_daisy: aa5500ff(38)
Dec  1 18:26:19 mercury kernel: parport0: assign_addrs: aa5500ff(38)
(Continue reading)

Adrian Bunk | 1 Dec 2006 23:33
Picon

[2.6 patch] paride: remove parport #ifdef's

CONFIG_PARIDE depends on CONFIG_PARPORT_PC, so there's no reason for 
these #ifdef's.

Signed-off-by: Adrian Bunk <bunk <at> stusta.de>

---

 drivers/block/paride/bpck6.c  |   13 -------------
 drivers/block/paride/paride.c |   33 ---------------------------------
 2 files changed, 46 deletions(-)

--- linux-2.6.19-rc6-mm2/drivers/block/paride/bpck6.c.old	2006-12-01 23:14:49.000000000 +0100
+++ linux-2.6.19-rc6-mm2/drivers/block/paride/bpck6.c	2006-12-01 23:15:09.000000000 +0100
 <at>  <at>  -31,10 +31,7  <at>  <at>  static int verbose; /* set this to 1 to 
 #include <linux/slab.h>
 #include <linux/types.h>
 #include <asm/io.h>
-
-#if defined(CONFIG_PARPORT_MODULE)||defined(CONFIG_PARPORT)
 #include <linux/parport.h>
-#endif

 #include "ppc6lnx.c"
 #include "paride.h"
 <at>  <at>  -139,11 +136,6  <at>  <at>  static int bpck6_test_port ( PIA *pi )  
 	PPCSTRUCT(pi)->ppc_id=pi->unit;
 	PPCSTRUCT(pi)->lpt_addr=pi->port;

-#ifdef CONFIG_PARPORT_PC_MODULE
-#define CONFIG_PARPORT_PC
(Continue reading)

Adrian Bunk | 1 Dec 2006 23:35
Picon

[2.6 patch] remove drivers/block/paride/jumbo

Let's remove this pre-historic paride building script.

Signed-off-by: Adrian Bunk <bunk <at> stusta.de>

---

 drivers/block/paride/jumbo |   70 -------------------------------------
 1 file changed, 70 deletions(-)

--- linux-2.6.19-rc6-mm2/drivers/block/paride/jumbo	2006-09-20 05:42:06.000000000 +0200
+++ /dev/null	2006-09-19 00:45:31.000000000 +0200
 <at>  <at>  -1,70 +0,0  <at>  <at> 
-#!/bin/sh
-#
-# This script can be used to build "jumbo" modules that contain the
-# base PARIDE support, one protocol module and one high-level driver.
-#
-echo -n "High level driver [pcd] : "
-read X
-HLD=${X:-pcd}
-#
-echo -n "Protocol module [bpck] : "
-read X
-PROTO=${X:-bpck}
-#
-echo -n "Use MODVERSIONS [y] ? "
-read X
-UMODV=${X:-y}
-#
-echo -n "For SMP kernel [n] ? "
(Continue reading)

Alan | 1 Dec 2006 23:49
Picon

Re: [2.6 patch] remove drivers/block/paride/jumbo

On Fri, 1 Dec 2006 23:35:21 +0100
Adrian Bunk <bunk <at> stusta.de> wrote:

> Let's remove this pre-historic paride building script.
> 
> Signed-off-by: Adrian Bunk <bunk <at> stusta.de>

Acked-by: Alan Cox <alan <at> redhat.com>
Alan | 1 Dec 2006 23:50
Picon

Re: [2.6 patch] paride: remove parport #ifdef's

On Fri, 1 Dec 2006 23:33:15 +0100
Adrian Bunk <bunk <at> stusta.de> wrote:

> CONFIG_PARIDE depends on CONFIG_PARPORT_PC, so there's no reason for 
> these #ifdef's.
> 
> Signed-off-by: Adrian Bunk <bunk <at> stusta.de>

Acked-by: Alan Cox <alan <at> redhat.com>
Mark Hindley | 1 Dec 2006 19:35
Picon

Re: Parport data not tristated after use

I have compiled the  modules with DEBUG_PARPORT. The log files are
below. I hope that helps.

Thanks

Mark

Dec  1 18:26:19 mercury kernel: pnp: the driver 'parport_pc' has been registered
Dec  1 18:26:19 mercury kernel: pnp: match found with the PnP device '00:09' and the driver 'parport_pc'
Dec  1 18:26:19 mercury kernel: pnp: Res cnt 3
Dec  1 18:26:19 mercury kernel: pnp: res cnt 3
Dec  1 18:26:19 mercury kernel: pnp: Encode io
Dec  1 18:26:19 mercury kernel: pnp: Encode io
Dec  1 18:26:19 mercury kernel: pnp: Encode irq
Dec  1 18:26:19 mercury kernel: pnp: Device 00:09 activated.
Dec  1 18:26:19 mercury kernel: parport: PnPBIOS parport detected.
Dec  1 18:26:19 mercury kernel: __parport_pc_frob_control(20,20): 0c -> 2c
Dec  1 18:26:19 mercury kernel: parport_pc_write_data(c9d13800,0x55)
Dec  1 18:26:19 mercury kernel: parport_pc_read_data(c9d13800) = 0xff
Dec  1 18:26:19 mercury kernel: parport_pc_write_data(c9d13800,0xaa)
Dec  1 18:26:19 mercury kernel: parport_pc_read_data(c9d13800) = 0xff
Dec  1 18:26:19 mercury kernel: __parport_pc_frob_control(20,00): 2c -> 0c
Dec  1 18:26:19 mercury kernel: parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
Dec  1 18:26:19 mercury kernel: parport_pc_write_data(c9d13800,0x00)
Dec  1 18:26:19 mercury kernel: __parport_pc_frob_control(20,00): 0c -> 0c
Dec  1 18:26:19 mercury kernel: parport0: cpp_daisy: aa5500ff(38)
Dec  1 18:26:19 mercury kernel: parport0: assign_addrs: aa5500ff(38)
Dec  1 18:26:19 mercury kernel: parport0: Peripheral not IEEE1284 compliant (0xDE)
Dec  1 18:26:19 mercury kernel: parport0: cpp_daisy: aa5500ff(38)
Dec  1 18:26:19 mercury kernel: parport0: assign_addrs: aa5500ff(38)
(Continue reading)

Dominik Brodowski | 5 Dec 2006 03:17

[PATCH 5/9] pcmcia: conf.ConfigBase and conf.Present consolidation

From: Dominik Brodowski <linux <at> dominikbrodowski.net>
Date: Wed, 25 Oct 2006 21:49:27 -0400
Subject: [PATCH] pcmcia: conf.ConfigBase and conf.Present consolidation

struct pcmcia_device *p_dev->conf.ConfigBase and .Present are set in almost
all PCMICA driver right at the beginning, using the same calls but slightly
different implementations. Unfiy this in the PCMCIA core.

Includes a small bugfix ("drivers/net/pcmcia/xirc2ps_cs.c: remove unused
label") from and Signed-off-by Adrian Bunk <bunk <at> stusta.de>

Signed-off-by: Dominik Brodowski <linux <at> dominikbrodowski.net>
---
 drivers/ata/pata_pcmcia.c               |    7 -----
 drivers/bluetooth/bluecard_cs.c         |   38 +------------------------------
 drivers/bluetooth/bt3c_cs.c             |   20 +---------------
 drivers/bluetooth/btuart_cs.c           |   20 +---------------
 drivers/bluetooth/dtl1_cs.c             |   20 +---------------
 drivers/char/pcmcia/cm4000_cs.c         |   20 ----------------
 drivers/char/pcmcia/cm4040_cs.c         |   20 ----------------
 drivers/char/pcmcia/synclink_cs.c       |    7 -----
 drivers/ide/legacy/ide-cs.c             |    6 -----
 drivers/isdn/hardware/avm/avm_cs.c      |   22 ------------------
 drivers/isdn/hisax/avma1_cs.c           |   22 ------------------
 drivers/isdn/hisax/elsa_cs.c            |   17 -------------
 drivers/isdn/hisax/sedlbauer_cs.c       |   10 --------
 drivers/isdn/hisax/teles_cs.c           |   17 -------------
 drivers/net/pcmcia/3c574_cs.c           |   16 +++---------
 drivers/net/pcmcia/3c589_cs.c           |    7 -----
 drivers/net/pcmcia/axnet_cs.c           |    6 +----
(Continue reading)

Karsten Keil | 6 Dec 2006 00:36
Picon

Re: [PATCH 5/9] pcmcia: conf.ConfigBase and conf.Present consolidation

On Mon, Dec 04, 2006 at 09:17:16PM -0500, Dominik Brodowski wrote:
> From: Dominik Brodowski <linux <at> dominikbrodowski.net>
> Date: Wed, 25 Oct 2006 21:49:27 -0400
> Subject: [PATCH] pcmcia: conf.ConfigBase and conf.Present consolidation
> 
> struct pcmcia_device *p_dev->conf.ConfigBase and .Present are set in almost
> all PCMICA driver right at the beginning, using the same calls but slightly
> different implementations. Unfiy this in the PCMCIA core.
> 
> Includes a small bugfix ("drivers/net/pcmcia/xirc2ps_cs.c: remove unused
> label") from and Signed-off-by Adrian Bunk <bunk <at> stusta.de>
> 
> Signed-off-by: Dominik Brodowski <linux <at> dominikbrodowski.net>
> ---
>  drivers/ata/pata_pcmcia.c               |    7 -----
>  drivers/bluetooth/bluecard_cs.c         |   38 +------------------------------
>  drivers/bluetooth/bt3c_cs.c             |   20 +---------------
>  drivers/bluetooth/btuart_cs.c           |   20 +---------------
>  drivers/bluetooth/dtl1_cs.c             |   20 +---------------
>  drivers/char/pcmcia/cm4000_cs.c         |   20 ----------------
>  drivers/char/pcmcia/cm4040_cs.c         |   20 ----------------
>  drivers/char/pcmcia/synclink_cs.c       |    7 -----
>  drivers/ide/legacy/ide-cs.c             |    6 -----

>  drivers/isdn/hardware/avm/avm_cs.c      |   22 ------------------
>  drivers/isdn/hisax/avma1_cs.c           |   22 ------------------
>  drivers/isdn/hisax/elsa_cs.c            |   17 -------------
>  drivers/isdn/hisax/sedlbauer_cs.c       |   10 --------
>  drivers/isdn/hisax/teles_cs.c           |   17 -------------

(Continue reading)

Jean Delvare | 17 Dec 2006 17:40
Gravatar

[PATCH] parport_pc: Fix parport_pc_probe_port section warning

WARNING: drivers/parport/parport_pc.o - Section mismatch: reference
to .init.text: from .text between 'parport_pc_probe_port' (at offset
0x14f7) and 'parport_pc_unregister_port'

parport_dma_probe() cannot be declared __devinit as it is called
from parport_pc_probe_port() which isn't.

Signed-off-by: Jean Delvare <khali <at> linux-fr.org>
---
 drivers/parport/parport_pc.c |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

--- linux-2.6.20-rc1.orig/drivers/parport/parport_pc.c	2006-12-17 16:08:05.000000000 +0100
+++ linux-2.6.20-rc1/drivers/parport/parport_pc.c	2006-12-17 17:36:47.000000000 +0100
 <at>  <at>  -1546,7 +1546,7  <at>  <at> 
 }
 #endif /* CONFIG_PARPORT_PC_SUPERIO */

-static int __devinit get_superio_dma (struct parport *p)
+static int get_superio_dma (struct parport *p)
 {
 	int i=0;
 	while( (superios[i].io != p->base) && (i<NR_SUPERIOS))
 <at>  <at>  -2106,7 +2106,7  <at>  <at> 
 /* --- DMA detection -------------------------------------- */

 /* Only if chipset conforms to ECP ISA Interface Standard */
-static int __devinit programmable_dma_support (struct parport *p)
+static int programmable_dma_support (struct parport *p)
 {
(Continue reading)


Gmane