Menu
▾
▴
linux-apus-devel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(210) |
Jun
(169) |
Jul
(167) |
Aug
(128) |
Sep
(218) |
Oct
(120) |
Nov
(86) |
Dec
(71) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(91) |
Feb
(179) |
Mar
(52) |
Apr
(56) |
May
(183) |
Jun
(62) |
Jul
(63) |
Aug
(49) |
Sep
(36) |
Oct
(35) |
Nov
(72) |
Dec
(30) |
| 2002 |
Jan
(53) |
Feb
(61) |
Mar
(56) |
Apr
(13) |
May
(1) |
Jun
(7) |
Jul
(80) |
Aug
(73) |
Sep
(30) |
Oct
(29) |
Nov
(8) |
Dec
(40) |
| 2003 |
Jan
(10) |
Feb
(2) |
Mar
(4) |
Apr
(9) |
May
(3) |
Jun
(19) |
Jul
(64) |
Aug
(53) |
Sep
(28) |
Oct
(7) |
Nov
(3) |
Dec
(21) |
| 2004 |
Jan
(11) |
Feb
(30) |
Mar
(18) |
Apr
(1) |
May
(13) |
Jun
(18) |
Jul
(13) |
Aug
|
Sep
(9) |
Oct
(5) |
Nov
|
Dec
|
| 2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(10) |
Aug
(21) |
Sep
(7) |
Oct
(10) |
Nov
(6) |
Dec
|
| 2006 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
(6) |
Oct
(10) |
Nov
(8) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(6) |
Mar
(1) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(13) |
Aug
(8) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: Frank R. G. P. <pe...@he...> - 2001-02-14 12:20:18
|
On Wed, Feb 14, 2001 at 12:39:56PM +0100, Geert Uytterhoeven wrote:
> Does it work if you put a `mb()' in between any two accesses of CIA registers?
That is essentially it if you replace the dprintk with mb(). IIRC every access
to the CIA has a DPRINTK right above it.
--
Dipl. Informatikingenieur ETH Frank Petzold <pe...@he...>
ceterum censeo parvomollem esse delendam.
|
|
From: Geert U. <ge...@li...> - 2001-02-14 11:41:02
|
On Wed, 14 Feb 2001, Frank Rudolf Georg Petzold wrote:
> On Tue, Feb 13, 2001 at 04:24:59PM +0100, Geert Uytterhoeven wrote:
> > What happens if you replace the DPRINTK(...) by mb()?
>
> I confirm that it somewhat works with debug enabled. Configuration:
> 604e/233, 70ns RAM, CV64/3D with 1280x1024-8, XFree 4.0.2 running.
> Somwhat means that the data is not entirely correct when arriving at the
> printer (I have a PostScript printer). Therefore I get strange results, but
> most of it is still readable.
>
> If I replace the printk with mb() it does not work at all.
>
> > The fact that it works for some people could be attributed to the CPU (603e vs.
> > 604e).
>
> It seems to be partially a tming problem, but not entirely. As I said, I once
> inserted delay loops that would only allow to write about 1 Bps to the CIA, but
> that did not help. There must be more to the dprintk call.
Does it work if you put a `mb()' in between any two accesses of CIA registers?
What is the definition of `mb()' in the APUS tree nowadays? Plain 2.4.2-pre3
has (include/asm-ppc/system.h):
| #define mb() __asm__ __volatile__ ("sync" : : : "memory")
| #define rmb() __asm__ __volatile__ ("sync" : : : "memory")
| #define wmb() __asm__ __volatile__ ("eieio" : : : "memory")
Side question: does it work under Linux/m68k?
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
|
|
From: T. <Ren...@gm...> - 2001-02-14 11:26:15
|
Hello out there! Yesterday I downloaded the whole 2.3 tree from sourceforge CVS and tried to compile. But during almost all attempts I got some strange internal errors due to fatal signal 11 (sometimes 4). I always restarts after that without doing a dep clean again. These errors occurs at different points of compilation, they are not predictable! I attach one of these errors as file signal. I also attach the gzipped config I used yesterday and today morning (I did not try to compile it with disabling all parallel stuff yet) with the error it always reported today (file error). I also got a huge error/warning output after compiler has entered and compiled some parts of ../ppc/amiga (I don't know if it was this directory or one of the following). The output covers more then 3! whole displays (1024x786)!! I already posted it some weeks ago (it seems to be the same), but if somebody is interested, I'll try to get it again. The error file I attach is the one I got today morning while the latest compilation attempt was started! Meanwhile I think I've the buggiest Linux of all! Nothing works, neither 2.4 comilation nor CD-burning (I've got 2 blank CDs with 4MB on them, cdrecord made with the only 2.4 kernel I ever made; after 4 MB some kind of timeout occurs!; I won't take this 2.4 kernel again, cause it hangs the whole Linux after a while (have to press Ctrl-Amiga-Amiga then)!)! I hope somebody is able to help! I would like to have a working 2.4 kernel, but I'd more like to have one working Cd-burning software! Thanx again Kind regards -- ======================== René Thol ------------------------------------ Multimedia Computing University of Ulm ======================== E-Mail: Ren...@gm... ======================== |
|
From: Ken T. <ke...@we...> - 2001-02-14 06:44:54
|
On Mon, 12 Feb 2001, Alan Buxey wrote: Not sure what actually *works* but : > CONFIG_PARPORT=y > # CONFIG_PARPORT_PC is not set > CONFIG_PARPORT_AMIGA=y compiles OK but : > iirc, only CONFIG_M68K_PRINTER=y complains about undefined lp_m68k_init reference. Ken. |
|
From: Frank R. G. P. <pe...@he...> - 2001-02-13 23:36:51
|
On Tue, Feb 13, 2001 at 04:24:59PM +0100, Geert Uytterhoeven wrote:
> What happens if you replace the DPRINTK(...) by mb()?
I confirm that it somewhat works with debug enabled. Configuration:
604e/233, 70ns RAM, CV64/3D with 1280x1024-8, XFree 4.0.2 running.
Somwhat means that the data is not entirely correct when arriving at the
printer (I have a PostScript printer). Therefore I get strange results, but
most of it is still readable.
If I replace the printk with mb() it does not work at all.
> The fact that it works for some people could be attributed to the CPU (603e vs.
> 604e).
It seems to be partially a tming problem, but not entirely. As I said, I once
inserted delay loops that would only allow to write about 1 Bps to the CIA, but
that did not help. There must be more to the dprintk call.
BTW, I have not been on IRC for some time, is some of you around there
sometimes?
--
Dipl. Informatikingenieur ETH Frank Petzold <pe...@he...>
ceterum censeo parvomollem esse delendam.
|
|
From: Glenn H. <gh...@c2...> - 2001-02-13 22:19:08
|
On 13-Feb-01, Robert wrote: > On Tue, Feb 13, 2001 at 05:45:39PM +0100, Glenn Hisdal wrote: >>> I did some tests with printing yesterday. >>> If I enable DEBUG in drivers/parport/parport_amiga.c, >>> printing works. >>> Without DEBUG disabled it only prints garbage (when printing >>> postscript files). > Funny thing... Before i wrote that printig was kind'a ok ... now no > matter > what i do it's all screwed really bad =o(( > I tried define DPRINTK mb() and enabled DEBUG and it doesn't change a > thing... ok. #define DPRINTK mb() didn't work here either, but it does work with DEBUG enabled. Use the #define DPRINTK printk(...) that is allready in the file when using DEBUG. (don't change it to mb() ). Also, I have not tried to compile it as a module, so I don't know if that works here. iirc we used #CONFIG_M68K_PRINTER=Y in 2.2.x to make printing work. When this is enabled functions from drivers/char/lp_m68k.c is used (hope I remembered the filename correctly). This file does not exist in 2.3. It has got it's own init function for example. It could probably be something in there that's needed to make printing work properly. - glenn |
|
From: Robert R. <ro...@pl...> - 2001-02-13 16:59:17
|
On Tue, Feb 13, 2001 at 05:45:39PM +0100, Glenn Hisdal wrote: > > > I did some tests with printing yesterday. > > > If I enable DEBUG in drivers/parport/parport_amiga.c, > > > printing works. > > > > Without DEBUG disabled it only prints garbage (when printing postscript > > > files). Funny thing... Before i wrote that printig was kind'a ok ... now no matter what i do it's all screwed really bad =o(( I tried define DPRINTK mb() and enabled DEBUG and it doesn't change a thing... In the meantime i've only changed to selfmade kernel 2.4.1 (with pci fixes)... Glenn could You send me Your .config ? (one more thing to note thou.. i didn't recompile whole kernel just the modules <<and the only file that i was changing is parport_amiga.c) *If* i'll have time tomorow i'll reboot with 2.4.0 that i was using previously and see how is printing going there (again) > ok. I have a 604e btw. 603e here... -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Frank R. G. P. <pe...@he...> - 2001-02-13 16:26:59
|
On Tue, Feb 13, 2001 at 05:04:13PM +0100, Glenn Hisdal wrote:
> Frank Rudolf Georg Petzold wrote:
> Timing problem ?
Hmm, I did some more extensive tests with delay loops in various places,
in the end essentially sending only one byte a second to the printer. Still,
there was garbage in the output (not all characters were garbage, but some).
I will try with DEBUG tonight.
What I really find wierd, we had exactly the same situation in 2.2. Until
someone fixed it. And the problem was IIRC not in parport_amiga.
--
Dipl. Informatikingenieur ETH Frank Petzold <pe...@he...>
ceterum censeo parvomollem esse delendam.
|
|
From: Glenn H. <gh...@c2...> - 2001-02-13 15:45:03
|
Geert Uytterhoeven wrote: > > On Tue, 13 Feb 2001, Glenn Hisdal wrote: > > Frank Rudolf Georg Petzold wrote: > > > On Tue, Feb 13, 2001 at 11:41:20AM +0100, Ren? Thol wrote: > > > > And how do I compile a 2.4 kernel that can use my printer on the > > > > parallel port? > > > > > > There is no way. Parallel port support is broken in 2.4. Use 2.2 instead. > > > > I did some tests with printing yesterday. > > If I enable DEBUG in drivers/parport/parport_amiga.c, > > printing works. > > Without DEBUG disabled it only prints garbage (when printing postscript > > files). [..] > > So, I turned off DEBUG and added a for-loop inside > > amiga_write_control(..) > > to add a small delay, and printing still worked... > > > > Timing problem ? > > What happens if you replace the DPRINTK(...) by mb()? > I'll try that tonight, and see what happens... > The fact that it works for some people could be attributed to the CPU (603e vs. > 604e). ok. I have a 604e btw. - glenn |
|
From: Geert U. <ge...@li...> - 2001-02-13 15:25:44
|
On Tue, 13 Feb 2001, Glenn Hisdal wrote:
> Frank Rudolf Georg Petzold wrote:
> > On Tue, Feb 13, 2001 at 11:41:20AM +0100, Ren? Thol wrote:
> > > And how do I compile a 2.4 kernel that can use my printer on the
> > > parallel port?
> >
> > There is no way. Parallel port support is broken in 2.4. Use 2.2 instead.
>
> I did some tests with printing yesterday.
> If I enable DEBUG in drivers/parport/parport_amiga.c,
> printing works.
> The only problem is that a page containing only one letter is printed
> out after it's done with what it was supposed to print out.
>
> Without DEBUG disabled it only prints garbage (when printing postscript
> files).
>
> So, I thought maybe it tried to send data faster than the Amiga
> parallell port (or the printer) could handle or something. (since
> writing the debug output will add a short delay)
>
> So, I turned off DEBUG and added a for-loop inside
> amiga_write_control(..)
> to add a small delay, and printing still worked...
>
> Timing problem ?
What happens if you replace the DPRINTK(...) by mb()?
The fact that it works for some people could be attributed to the CPU (603e vs.
604e).
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
|
|
From: Glenn H. <gh...@c2...> - 2001-02-13 15:03:48
|
Frank Rudolf Georg Petzold wrote: > > On Tue, Feb 13, 2001 at 11:41:20AM +0100, Ren? Thol wrote: > > And how do I compile a 2.4 kernel that can use my printer on the > > parallel port? > > There is no way. Parallel port support is broken in 2.4. Use 2.2 instead. I did some tests with printing yesterday. If I enable DEBUG in drivers/parport/parport_amiga.c, printing works. The only problem is that a page containing only one letter is printed out after it's done with what it was supposed to print out. Without DEBUG disabled it only prints garbage (when printing postscript files). So, I thought maybe it tried to send data faster than the Amiga parallell port (or the printer) could handle or something. (since writing the debug output will add a short delay) So, I turned off DEBUG and added a for-loop inside amiga_write_control(..) to add a small delay, and printing still worked... Timing problem ? the config used (from memory, so it may not me the correct names) CONFIG_PARPORT=Y CONFIG_PARPORT_AMIGA=Y CONFIG_PRINTER=Y CONFIG_M68K_PRINTER does not work as that needs some functions found in lp_m68k.c which we don't have in 2.4. - glenn |
|
From: Michel <mic...@ii...> - 2001-02-13 13:24:43
|
Ren=E9 Thol wrote: > > If you have run make dep after checking out or updating the source th= en it > > means that the dependencies don't work as they should. >=20 > And how do I get them work (I tried compiling with and without make dep > clean before starting make) Fix the code. ;) Anyway, I'm not sure anymore that's the problem... > > > And how do I compile a 2.4 kernel that can use my printer on the > > > parallel port? > > > > In 'General setup', select 'Parallel port setup' and then 'Amiga buil= tin > > port'. Your mileage will vary - It doesn't work for Frank while Rober= t > > says it kinda works for him. >=20 > As I said: I already tried, but could not compile! Now I can not even > compile my already compiled config! Weird. I just tried your config, built fine. Then I enabled parallel port support and it built. I disabled it again and it still built. When did you last update your source? Looks like it was before 2.4.1. What gcc and binutils do you have? (gcc -v and ld -v) --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
|
From: Alan B. <al...@ms...> - 2001-02-13 13:19:54
|
hi,
> > problem. There were some fixes to the 68k tree recently which involved
^^^^^^^^
> > the 'media select' issue..i'm sure.
> >
>
> Does this mean I should get the 2.3 tree again (would be no problem) and
> compile it?
we dont use the 68k tree
> I does not know exactly, but it recognizes the YAMAHA with ID 6, LUN 0 and so
> on.
it seems to
alan
|
|
From: Michel <mic...@ii...> - 2001-02-13 13:19:04
|
Ren=E9 Thol wrote: > > > I followed up all steps described in CD-Writing-HOWTO, but the resu= lt is > > > attatched! > > > > sorry, I forgot, you have SCSI - I still think its a device refreshin= g > > problem. There were some fixes to the 68k tree recently which involv= ed > > the 'media select' issue..i'm sure. >=20 > Does this mean I should get the 2.3 tree again (would be no problem) an= d > compile it? You don't have to 'get it again', just run 'cvs update' and 'make oldconf= ig dep'. --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
|
From: T. <Ren...@gm...> - 2001-02-13 13:14:59
|
Hi Alan! Alan Buxey schrieb: > hi, > > > I followed up all steps described in CD-Writing-HOWTO, but the result is > > attatched! > > sorry, I forgot, you have SCSI - I still think its a device refreshing > problem. There were some fixes to the 68k tree recently which involved > the 'media select' issue..i'm sure. > Does this mean I should get the 2.3 tree again (would be no problem) and compile it? > > what does 'cdrecord -scanbus' give you > I does not know exactly, but it recognizes the YAMAHA with ID 6, LUN 0 and so on. Thanx Bye -- ======================== René Thol ------------------------------------ Multimedia Computing University of Ulm ======================== E-Mail: Ren...@gm... ======================== |
|
From: Alan B. <al...@ms...> - 2001-02-13 13:08:47
|
hi, > I followed up all steps described in CD-Writing-HOWTO, but the result is > attatched! sorry, I forgot, you have SCSI - I still think its a device refreshing problem. There were some fixes to the 68k tree recently which involved the 'media select' issue..i'm sure. what does 'cdrecord -scanbus' give you alan |
|
From: Alan B. <al...@ms...> - 2001-02-13 13:07:35
|
hi, > (SCSI) CD-writer! I'm really angry with Linux which is not able to burn > CDs neither using cdrecord, cdrdao nor cdwrite!!! Its nothign to do with Linux. I can guarantee that if you took an x86 boxen with Linux it'd work. thousands of people do every day. > How do you burn your CDs? Is there anybody who burns using Linux? Why > dos this not work? I dont burn my CD's under Linux. I've seen the IDE accessing under Linux/APUS and use MakeCD under AmigaOS. this may change in the future. > I followed up all steps described in CD-Writing-HOWTO, but the result is > attatched! obviously, as seen in the results of the burn there is a problem with the refreshing of the device (and access?) the media-select error appears when drives cannot respond in time when their status has changed (iirc!) I had to swap my ole trusty NEC 4X IDE ATAPI for a Creative 52X ATAPI to get around this myself for just plain CD access. I wonder if there are some tools/diags you can run on your controller alan |
|
From: T. <Ren...@gm...> - 2001-02-13 13:00:40
|
Hello again Michel Dänzer schrieb: > René Thol wrote: > > ... > If you have run make dep after checking out or updating the source then it > means that the dependencies don't work as they should. > And how do I get them work (I tried compiling with and without make dep clean before starting make) > > > And how do I compile a 2.4 kernel that can use my printer on the > > parallel port? > > In 'General setup', select 'Parallel port setup' and then 'Amiga builtin > port'. Your mileage will vary - It doesn't work for Frank while Robert says it > kinda works for him. As I said: I already tried, but could not compile! Now I can not even compile my already compiled config! Thanx Regards -- ======================== René Thol ------------------------------------ Multimedia Computing University of Ulm ======================== E-Mail: Ren...@gm... ======================== |
|
From: Michel <mic...@ii...> - 2001-02-13 12:54:33
|
Ren=E9 Thol wrote: > drivers/block/block.o: In function `device_init': > drivers/block/block.o(.text.init+0xe0): undefined reference to > `parport_init' > drivers/block/block.o(.text.init+0xe0): relocation truncated to fit: > R_PPC_REL24 parport_init > drivers/char/char.o: In function `chr_dev_init': > drivers/char/char.o(.text.init+0x258): undefined reference to `lp_init' > drivers/char/char.o(.text.init+0x258): relocation truncated to fit: > R_PPC_REL24 lp_init > make: *** [vmlinux] Error 1 >=20 > What does this mean? And why could I not compile the same config again= ? If you have run make dep after checking out or updating the source then i= t means that the dependencies don't work as they should. > And how do I compile a 2.4 kernel that can use my printer on the > parallel port? In 'General setup', select 'Parallel port setup' and then 'Amiga builtin port'. Your mileage will vary - It doesn't work for Frank while Robert sa= ys it kinda works for him. --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
|
From: Frank R. G. P. <pe...@he...> - 2001-02-13 11:25:42
|
On Tue, Feb 13, 2001 at 11:41:20AM +0100, Ren? Thol wrote:
> And how do I compile a 2.4 kernel that can use my printer on the
> parallel port?
There is no way. Parallel port support is broken in 2.4. Use 2.2 instead.
--
Dipl. Informatikingenieur ETH Frank Petzold <pe...@he...>
ceterum censeo parvomollem esse delendam.
|
|
From: T. <Ren...@gm...> - 2001-02-13 10:39:47
|
Hello everybody!
Yesterday I finally got a 2.4 kernel compiled with the attatched config!
After that I played a little with this config and tried different
compilations, but none of them succeded! So I thought I'll try the
original config with what I got the running kernel compiled and so I
compiled it again. But that did not work! (I started different tries and
there were also no empty .a or .o files)! I always got the following
error:
ld -T arch/ppc/vmlinux.lds -Ttext 0xc0000000 -Bstatic
arch/ppc/kernel/head.o init/main.o init/version.o \
--start-group \
arch/ppc/kernel/kernel.o arch/ppc/mm/mm.o arch/ppc/lib/lib.o
kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o arch/ppc/amiga/amiga.o \
drivers/block/block.o drivers/char/char.o drivers/misc/misc.o
drivers/net/net.o drivers/media/media.o drivers/scsi/scsidrv.o
drivers/cdrom/driver.o drivers/sound/sounddrivers.o
drivers/zorro/driver.o drivers/video/video.o \
net/network.o \
/usr/src/linux/lib/lib.a \
--end-group \
-o vmlinux
drivers/block/block.o: In function `device_init':
drivers/block/block.o(.text.init+0xe0): undefined reference to
`parport_init'
drivers/block/block.o(.text.init+0xe0): relocation truncated to fit:
R_PPC_REL24 parport_init
drivers/char/char.o: In function `chr_dev_init':
drivers/char/char.o(.text.init+0x258): undefined reference to `lp_init'
drivers/char/char.o(.text.init+0x258): relocation truncated to fit:
R_PPC_REL24 lp_init
make: *** [vmlinux] Error 1
What does this mean? And why could I not compile the same config again?
And how do I compile a 2.4 kernel that can use my printer on the
parallel port?
Questions and more questions!
Many thanx for your already provided assistance!
Kind regards
--
========================
René Thol
------------------------------------
Multimedia Computing
University of Ulm
========================
E-Mail: Ren...@gm...
========================
|
|
From: T. <Ren...@gm...> - 2001-02-13 10:32:29
|
Hello everybody! Yesterday I luckily managed to compile an own 2.4 kernel (all 2.4 versions from sourceforge do not work with my Linux). So I quickly tried to burn a CD; thought that this will work now! But id did not! I've got the cdrecord output attatched! I hope there might be finally anybody who can tell me how to burn CDs using Linux! I've got SuSE6.4 PPC installed, using 2.4 kernel and own a YAMAHA 8/4/24 (SCSI) CD-writer! I'm really angry with Linux which is not able to burn CDs neither using cdrecord, cdrdao nor cdwrite!!! How do you burn your CDs? Is there anybody who burns using Linux? Why dos this not work? I followed up all steps described in CD-Writing-HOWTO, but the result is attatched! Many thanx Kind regards -- ======================== René Thol ------------------------------------ Multimedia Computing University of Ulm ======================== E-Mail: Ren...@gm... ======================== |
|
From: Michel <mic...@ii...> - 2001-02-13 07:30:54
|
Glenn Hisdal wrote:
> >> I haven't been able to commit the patch yet because cvs tells me tha=
t I
> >> don't have write permission to the repository.
>=20
> > You probably checked it out anonymously. Change CVS/Root to
> > 'tur...@cv...:/cvsroot/linux-apus' and the=
n
> > copy it to all the Root files with 'find -name Root -exec cp CVS/Root=
{}
> > \;'
>=20
> Thanks.
> I have just commited it.
> Hope everything went well :-)
Looks good. Congrats. :)
--=20
Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de=
veloper
CS student, Free Software enthusiast \ XFree86 and DRI project m=
ember
|
|
From: Glenn H. <gh...@c2...> - 2001-02-13 05:43:07
|
On 13-Feb-01, Roman wrote:
> Hi,
> On Mon, 12 Feb 2001, Glenn Hisdal wrote:
>> I haven't been able to commit the patch yet because cvs tells me that I
>> don't have write permission to the repository.
> You probably checked it out anonymously. Change CVS/Root to
> 'tur...@cv...:/cvsroot/linux-apus' and then
> copy it to all the Root files with 'find -name Root -exec cp CVS/Root {}
> \;'
Thanks.
I have just commited it.
Hope everything went well :-)
- glenn
|
|
From: Roman Z. <zi...@fh...> - 2001-02-13 00:18:43
|
Hi,
On Mon, 12 Feb 2001, Glenn Hisdal wrote:
> I haven't been able to commit the patch yet because cvs tells me that I
> don't have write permission to the repository.
You probably checked it out anonymously. Change CVS/Root to
'tur...@cv...:/cvsroot/linux-apus' and then
copy it to all the Root files with 'find -name Root -exec cp CVS/Root {} \;'
bye, Roman
|
107 messages has been excluded from this view by a project administrator.
