linux-apus-devel

Re: tilde key

[Roman Z. <zi...@li...>]

Hi,

Ken Tyler wrote:

> Have I lost my tilde key ?  Does it work for anyone ?

Somehow the initialization of the SYSRQ key got lost, it works now
again.

bye, Roman

CVS Update: 2.3 (branch: trunk)

[Roman Z. <zi...@us...>]

CVSROOT:	/cvsroot/linux-apus
Module name:	2.3
Repository:	2.3/arch/ppc/kernel/
Changes by:	zippel@usw-pr-cvs1.	01/11/08 11:05:58

Log message:
  initialize SYSRQ_KEY
  remove unused functions

Modified files:
      2.3/arch/ppc/kernel/:
        apus_setup.c 
  
  Revision      Changes    Path
  1.30          +1 -38     2.3/arch/ppc/kernel/apus_setup.c

CVS Update: 2.3 (branch: trunk)

[Roman Z. <zi...@us...>]

CVSROOT:	/cvsroot/linux-apus
Module name:	2.3
Repository:	2.3/arch/ppc/kernel/
Changes by:	zippel@usw-pr-cvs1.	01/11/07 17:21:23

Log message:
  irq fixes
  initialize ppc_kbd_sysrq_xlate

Modified files:
      2.3/arch/ppc/kernel/:
        apus_setup.c irq.c 
  
  Revision      Changes    Path
  1.29          +10 -12    2.3/arch/ppc/kernel/apus_setup.c
  1.13          +1 -1      2.3/arch/ppc/kernel/irq.c

Re: tilde key

[Roman Z. <zi...@li...>]

Hi,

Geert Uytterhoeven wrote:

> It's the key with keycode 0, right? On most architectures keycode 0 is ignored,
> we had an #ifdef to enable it. Perhaps someone reverted the code
> (drivers/char/vt.c, I think).

Hmm, I can't find any relevant change...
The strange thing is, shift+tilde works now as sysrq key?!
Any idea, how this could happen?

bye, Roman

Re: differences between 2.2 and 2.4 serial?

[Giorgio T. <de...@ip...>]

Hello Geert

...

> If they use the MC68681 (I think so, since the IOBlix has parallel port=
s as
> well), you can work together with J=F6rg Dorchain (IIRC the MFC3 uses t=
he same
> chip).

P.S. The parallel chip IOBlix Zorro2 uses is an EXAR ST78C36.


Regards
--=20
                                                 Giorgio Terzi

Re: differences between 2.2 and 2.4 serial?

[Giorgio T. <de...@ip...>]

Hello Geert

...
> On Mon, 5 Nov 2001, Giorgio Terzi wrote:
>> I am working with it for an 2.4.xx IOBlix serial driver and i am in
>> the debugging phase.
>> If the UARTs you use are Startech as IOBlix we may unify it ...
>=20
> Which Startech UART? A quick search on Google for `Startech UART' revea=
led
> they have both MC68681 and 16550 compatible parts.
>=20
> If they use the MC68681 (I think so, since the IOBlix has parallel port=
s as
> well), you can work together with J=F6rg Dorchain (IIRC the MFC3 uses t=
he same
> chip).

For IOBlix Zorro 2 is an Exar 16C654,=20
i am using a lot of low level things from Ted Ts'o PC serial driver becau=
se is
very similar.

Regards
--=20
                                                 Giorgio Terzi

Re: tilde key

[Giorgio T. <de...@ip...>]

On 06-Nov-01, Ken Tyler wrote:

> 
> Hello,
> 
> Have I lost my tilde key ?  Does it work for anyone ?
> 
> Ken
> 

The same for me!
the only way i have now to "negate" something is to use 
Alt-j space :))))

Regards
-- 
                                                 Giorgio Terzi

CVS Update: 2.3 (branch: trunk)

[Roman Z. <zi...@us...>]

CVSROOT:	/cvsroot/linux-apus
Module name:	2.3
Repository:	2.3/mm/
Changes by:	zippel@usw-pr-cvs1.	01/11/06 17:42:39

Log message:
  conflict fixes from import bitkeeper (2.4.14)

Modified files:
      ./:
        Makefile 
      2.3/Documentation/:
        Configure.help 
      2.3/arch/ppc/:
        defconfig 
      2.3/arch/ppc/configs/:
        apus_defconfig 
      2.3/arch/ppc/kernel/:
        apus_setup.c head.S ppc_ksyms.c setup.c 
      2.3/drivers/char/:
        Makefile 
      2.3/drivers/ide/:
        buddha.c ide.c 
      2.3/drivers/parport/:
        ieee1284.c ieee1284_ops.c 
      2.3/drivers/scsi/:
        amiga7xx.c fastlane.c 
      2.3/drivers/sound/dmasound/:
        dmasound_core.c dmasound_paula.c 
      2.3/include/asm-ppc/:
        io.h mpc8xx.h pgtable.h 
      2.3/mm/:
        page_alloc.c 
Removed files:
      2.3/arch/arm/def-configs/:
        bitsy cerf 
      2.3/drivers/acpi/:
        driver.h 
      2.3/drivers/acpi/executer/:
        exdyadic.c exmonad.c exxface.c 
      2.3/fs/cramfs/inflate/:
        Makefile adler32.c infblock.c infblock.h infcodes.c 
        infcodes.h inffast.c inffast.h inffixed.h inflate.c 
        inftrees.c inftrees.h infutil.c infutil.h uncompr.c 
        zconf.h zlib.h zutil.h 
  
  Revision      Changes    Path
  1.29          +1 -1      2.3/Makefile
  1.21          +121 -1    2.3/Documentation/Configure.help
  1.16          +9 -2      2.3/arch/ppc/defconfig
  1.14          +9 -2      2.3/arch/ppc/configs/apus_defconfig
  1.28          +1 -1      2.3/arch/ppc/kernel/apus_setup.c
  1.25          +1 -1      2.3/arch/ppc/kernel/head.S
  1.28          +3 -1      2.3/arch/ppc/kernel/ppc_ksyms.c
  1.21          +1 -1      2.3/arch/ppc/kernel/setup.c
  1.17          +1 -0      2.3/drivers/char/Makefile
  1.7           +18 -11    2.3/drivers/ide/buddha.c
  1.5           +3 -9      2.3/drivers/ide/ide.c
  1.4           +5 -3      2.3/drivers/parport/ieee1284.c
  1.4           +8 -9      2.3/drivers/parport/ieee1284_ops.c
  1.4           +4 -1      2.3/drivers/scsi/amiga7xx.c
  1.8           +1 -1      2.3/drivers/scsi/fastlane.c
  1.5           +1 -0      2.3/drivers/sound/dmasound/dmasound_core.c
  1.5           +1 -0      2.3/drivers/sound/dmasound/dmasound_paula.c
  1.13          +1 -1      2.3/include/asm-ppc/io.h
  1.6           +1 -1      2.3/include/asm-ppc/mpc8xx.h
  1.13          +1 -1      2.3/include/asm-ppc/pgtable.h
  1.20          +18 -22    2.3/mm/page_alloc.c

Re: differences between 2.2 and 2.4 serial?

[Alan B. <al...@ms...>]

hi,

> > I am working with it for an 2.4.xx IOBlix serial driver and i am in
> > the debugging phase.
> > If the UARTs you use are Startech as IOBlix we may unify it ...
>
> Which Startech UART? A quick search on Google for `Startech UART' revea=
led they
> have both MC68681 and 16550 compatible parts.
>
> If they use the MC68681 (I think so, since the IOBlix has parallel port=
s as
> well), you can work together with J=F6rg Dorchain (IIRC the MFC3 uses t=
he same
> chip).

the IOBlix1200 serial uses a 16550 compatible part - as does the hypercom

alan

Re: tilde key

[Geert U. <ge...@li...>]

On Tue, 6 Nov 2001, Ken Tyler wrote:
> Have I lost my tilde key ?  Does it work for anyone ?

It's the key with keycode 0, right? On most architectures keycode 0 is ignored,
we had an #ifdef to enable it. Perhaps someone reverted the code
(drivers/char/vt.c, I think).

Note that according to Andries Brouwer there exists a security problem if you
allow keycode 0, so alternatively you can remap it to an unused keycode number
in the Amiga keyboard driver. The disadvantage of that solution is that all
keymaps in all distros have to be modified as well.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

tilde key

[Ken T. <ke...@we...>]

Hello,

Have I lost my tilde key ?  Does it work for anyone ?

Ken

Re: differences between 2.2 and 2.4 serial?

[Geert U. <Gee...@so...>]

On Mon, 5 Nov 2001, Giorgio Terzi wrote:
> I am working with it for an 2.4.xx IOBlix serial driver and i am in
> the debugging phase.
> If the UARTs you use are Startech as IOBlix we may unify it ...

Which Startech UART? A quick search on Google for `Startech UART' reveale=
d they
have both MC68681 and 16550 compatible parts.

If they use the MC68681 (I think so, since the IOBlix has parallel ports =
as
well), you can work together with J=F6rg Dorchain (IIRC the MFC3 uses the=
 same
chip).

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6=
8k.org

In personal conversations with technical people, I call myself a hacker. =
But
when I'm talking to journalists I just say "programmer" or something like=
 that.
							    -- Linus Torvalds

Re: CVS Update: 2.3 (branch: trunk)

[Alan B. <al...@ms...>]

hi,

> I fixed it already, just run an update, but before put something like
> this into your .cvsrc:
>
> checkout -P
> update -d -P

:-) i know...i am SO embarressed about my thoughts of the lack of contents
in the 2.4.x tree (thought we'd lost sync a lot) ...

i've since copied my .cvsrc from my older system..duh!

alan

Re: differences between 2.2 and 2.4 serial

[Alan B. <al...@ms...>]

hi,

> m68kserial  interface is lost...(sigh!),
> one alternative is to use the new generic_serial meta_driver
> I am working with it for an 2.4.xx IOBlix serial driver and i am in
> the debugging phase.
> If the UARTs you use are Startech as IOBlix we may unify it ...

its the Ioblix1200 serial that i was looking at!

the reason why is that i use the hypercom module under 2.2.10 with my
ioblix1200 serial and it works 100% fine..... so if this was brought up to
2.4.x then we'd have a working driver for all the hypercom/ioblix1200
people out there

alan

Re: CVS Update: 2.3 (branch: trunk)

[Roman Z. <zi...@li...>]

Hi,

Alan Buxey wrote:

> I'll submit the re--refixed makefiles this evening if someone
> has not done so already

I fixed it already, just run an update, but before put something like
this into your .cvsrc:

checkout -P
update -d -P

bye, Roman

Re: differences between 2.2 and 2.4 serial?

[Giorgio T. <de...@ip...>]

Alan Buxey wrote:

> hi,
>
> can someone point me to a resource where i can easily see
> the changes made to the serial system between the
> 2.2.x and 2.4.x kernels?  We have various missing
> drivers that need to be updated....and i now have
> such hardware in my system after the recent WOASE 2001
>
> alan
>

m68kserial  interface is lost...(sigh!),
one alternative is to use the new generic_serial meta_driver
I am working with it for an 2.4.xx IOBlix serial driver and i am in
the debugging phase.
If the UARTs you use are Startech as IOBlix we may unify it ...

Regards

                Giorgio Terzi

Re: Grex support

[Alan B. <al...@ms...>]

hi,

> The software to scan the PCI bus can be used under AmigaOS only. We need to
> know what `the software to scan the PCI bus' itself does.
>
> An alternative is to reverse engineer `the software to scan the PCI bus'.

..and the same 'scanning the PCI BUS' needs to be done for the Medaitor
too....

I think the main issue is that none of us actually HAVE this hardware....

..also, as the Mediator works in 68k world i think we may find that the
68k-linux folks may get it running for us :-)

alan

Re: CVS Update: 2.3 (branch: trunk)

[Roman Z. <zi...@li...>]

Hi,

On Mon, 5 Nov 2001, Geert Uytterhoeven wrote:

> OK. But we still disable the IRQ during probing, right?

Yes.

> I still remember the hard hacking that lead to that change: some Western
> Digital Caviar drives didn't honour the ATA disable IRQ bit, so they caused an
> interrupt deadlock if you probed for them on Amiga with the IDE interrupt
> enabled. The problem didn't show up on PC because they had no shared
> interrupts, while on A4000 the IDE interrupt is shared with Zorro Ethernet,
> which was still enabled.

They have shared interrupts now too, but their interrupt is automatically
acknowledged.

bye, Roman

Re: CVS Update: 2.3 (branch: trunk)

[Geert U. <ge...@li...>]

On Mon, 5 Nov 2001, Roman Zippel wrote:
> On Mon, 5 Nov 2001, Geert Uytterhoeven wrote:
> > >   1.4           +89 -55    2.3/drivers/ide/ide-probe.c
> > >   1.4           +283 -171  2.3/drivers/ide/ide.c
> >
> > Since I was interested in seeing this fix, I diffed both files (against 1.3),
> > but it looks like lots of other things were changed, too. Is that correct?
>
> No, the number of changes are against the wrong file (1.3 is from
> 2.4.0-test2, also see the log), you want these diffs:

IC.

> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-apus/2.3/drivers/ide/ide.c.diff?r1=text&tr1=1.1.1.16&r2=text&tr2=1.4&diff_format=h
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-apus/2.3/drivers/ide/ide-probe.c.diff?r1=text&tr1=1.1.1.10&r2=text&tr2=1.4&diff_format=h
>
> The problem is that request_irq is between disable_irq/enable_irq and the
> ppc version of enable_irq doesn't like this, because request_irq resets
> the counter.

OK. But we still disable the IRQ during probing, right?

I still remember the hard hacking that lead to that change: some Western
Digital Caviar drives didn't honour the ATA disable IRQ bit, so they caused an
interrupt deadlock if you probed for them on Amiga with the IDE interrupt
enabled. The problem didn't show up on PC because they had no shared
interrupts, while on A4000 the IDE interrupt is shared with Zorro Ethernet,
which was still enabled.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: CVS Update: 2.3 (branch: trunk)

[Roman Z. <zi...@li...>]

Hi,

On Mon, 5 Nov 2001, Geert Uytterhoeven wrote:

> >   Revision      Changes    Path
> >   1.4           +89 -55    2.3/drivers/ide/ide-probe.c
> >   1.4           +283 -171  2.3/drivers/ide/ide.c
>
> Since I was interested in seeing this fix, I diffed both files (against 1.3),
> but it looks like lots of other things were changed, too. Is that correct?

No, the number of changes are against the wrong file (1.3 is from
2.4.0-test2, also see the log), you want these diffs:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-apus/2.3/drivers/ide/ide.c.diff?r1=text&tr1=1.1.1.16&r2=text&tr2=1.4&diff_format=h
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-apus/2.3/drivers/ide/ide-probe.c.diff?r1=text&tr1=1.1.1.10&r2=text&tr2=1.4&diff_format=h

The problem is that request_irq is between disable_irq/enable_irq and the
ppc version of enable_irq doesn't like this, because request_irq resets
the counter.
The other point is that SA_INTERRUPT is IMO only needed by broken intel
hardware, so there should be rather a ifdef __i386__...
Something else: ide_get_lock/ide_release_lock is only for atari anyway,
so does it need to be conditional during probe? I already removed the
ifdef's but I wasn't sure about this.

bye, Roman

Re: CVS Update: 2.3 (branch: trunk)

[Geert U. <ge...@li...>]

On Sun, 4 Nov 2001, Roman Zippel wrote:
> CVSROOT:	/cvsroot/linux-apus
> Module name:	2.3
> Repository:	2.3/drivers/ide/
> Changes by:	zippel@usw-pr-cvs1.	01/11/04 17:20:38
>
> Log message:
>   move disabling of interrupts during probe
>   enable other interrupts during ide irq
>
> Modified files:
>       2.3/drivers/ide/:
>         ide-probe.c ide.c
>
>   Revision      Changes    Path
>   1.4           +89 -55    2.3/drivers/ide/ide-probe.c
>   1.4           +283 -171  2.3/drivers/ide/ide.c

Since I was interested in seeing this fix, I diffed both files (against 1.3),
but it looks like lots of other things were changed, too. Is that correct?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

differences between 2.2 and 2.4 serial?

[Alan B. <al...@ms...>]

hi,

can someone point me to a resource where i can easily see
the changes made to the serial system between the
2.2.x and 2.4.x kernels?  We have various missing
drivers that need to be updated....and i now have
such hardware in my system after the recent WOASE 2001

alan

Re: CVS Update: 2.3 (branch: trunk)

[Alan B. <al...@ms...>]

hi,

I'll submit the re--refixed makefiles this evening if someone
has not done so already

alan

Re: CVS Update: 2.3 (branch: trunk)

[Alan B. <al...@ms...>]

hi,

> Alan, stop this _now_ and use cvs update -d please.

aarggh!  i'm *SO* sorry to have not noticed that i dont have
a .cvsrc under my account - REALLY sorry.

alan

Re: CVS Update: 2.3 (branch: trunk)

[Alan B. <al...@ms...>]

hi,

> >   Commented out the i2o entries - not APUS depended and contents not present
> >   (allows the `make dep` to work)
>
> What is the actual problem?

i2o contents are not present - unless my CVS tree is somehow missing
these?

alan