* Re: Re: 2.4.16 for algorithmics p6032
@ 2001-12-05 13:53 Zhang Fuxin
0 siblings, 0 replies; 2+ messages in thread
From: Zhang Fuxin @ 2001-12-05 13:53 UTC (permalink / raw)
To: Chris Dearman; +Cc: linux-mips@oss.sgi.com
hi,Chris,
you can do anything you like to my code:)
i have promised to release it months ago,but so busy I was the past
months and i am shy to release ugly code. Sorry if it waste you time.
Today I make some tests and get some fixes ,log is here
(i was too sleepy last night,so most of them is stupy errors):
2001.12.05:
arch/mips/defconfig-p6032:
ide dma unstable,don't choose 'use dma by default when available'
enable CONFIG_MTD_OBSOLETE_CHIPS & CONFIG_MTD_AMDSTD instead of
CONFIG_MTD_CFI_AMDSTD for p6032 flash driver
(to use the driver,mknod /dev/flash b 31 0,then you can cp to/from it)
arch/mips/kernel/time.c:
add code to display a banner using the little led on p6032.
arch/mips/algor/p6032/kernel/setup.c:
fix calculation of mips_counter_frequency,forget to div 2:(
the diff on my site is updated.
you probably will be more able to deal with the dma and board cache
than me:). The spurious interrupt problem still there,i have added some
code to work around it but don't know the reason.
I have made a quick test with ltp, most of them passed,but some of
the fs test and the syscall test failed,i will look into them soon
if you have interest,i can give you more detail results
在 2001-12-05 12:37:00 you wrote:
>Zhang Fuxin wrote:
>>
>> hi,linux-mips,
>>
>> This mail seems lost,so i repost,i apologize if it duplicates
>> :
>
> I've been tracking the 2.4 (now 2.5) kernel with my own P6032/P6064
>port. I did say I would send my stuff to Ralf to get it included in the
>CVS tree.
>
> I can see that you have some good stuff here, so I'd like to
>incorporate it into my code if that's OK with you. Then I *really* will
>send this stuff to Ralf.
>
> Regards
> Chris
>
>--
>Algorithmics,The Fruit Farm,Ely Road,Chittering,CAMBS CB5 9PH,ENGLAND
>P: +44 1223 706200 F: +44 1223 706250 W: http://www.algor.co.uk
Regards
Zhang Fuxin
fxzhang@ict.ac.cn
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: Re: 2.4.16 for algorithmics p6032
@ 2001-12-05 14:38 Zhang Fuxin
0 siblings, 0 replies; 2+ messages in thread
From: Zhang Fuxin @ 2001-12-05 14:38 UTC (permalink / raw)
To: Chris Dearman; +Cc: linux-mips@oss.sgi.com
hi,Chris,
在 2001-12-05 14:25:00 you wrote:
>Zhang Fuxin wrote:
>>
>> hi,Chris,
>> you can do anything you like to my code:)
>> i have promised to release it months ago,but so busy I was the past
>> months and i am shy to release ugly code. Sorry if it waste you time.
>
> Thanks. We've followed very similar routes so there aren't so many
>differences :-)
>
>>
>> Today I make some tests and get some fixes ,log is here
>> (i was too sleepy last night,so most of them is stupy errors):
>> 2001.12.05:
>> arch/mips/defconfig-p6032:
>> ide dma unstable,don't choose 'use dma by default when available'
>
> Yes. I have had a look at this but haven't tracked it down yet. The
>only thing I know is that the buffer heads get corrupted, so I assume
>there is some interrupt locking problem somewhere. I know that DMA
>works in the MIPS 2.4.3 port. Were you using DMA in your 2.4.8 kernel?
Yes,it works well,at least much more stable
for 2.4.16,a simple 'mtest01 -p80 -w'(alloc 80% memory to write) test can break the ide dma.
>
>> you probably will be more able to deal with the dma and board cache
>
> Do you use the IOBC? I had to make some changes to pci.h and the
>ethernet driver to make them work properly.
No. I had to make changes to generic code:),that's why i disable it.
>
>> than me:). The spurious interrupt problem still there,i have added some
>> code to work around it but don't know the reason.
>
> The spurious interrupts are caused by posted writes to PCI devices.
>The sequence is usually something like:
> o write device to clear interrupt (write gets posted)
> o enable CPU interrupts (interrupt is still pending)
> o CPU enters interrupt handler and reads 8259 which causes posted
>write
> to be flushed and so now there is no interrupt...
>
> The only fix is to do an explicit PCI (eg ISA port) before reenabling
>interrupts. The 2.4.x kernel reenables interrupts more quickly than the
>older kernel which is why it is more noticeable.
>
Oh, thanks for your explanation.
>>
>> I have made a quick test with ltp, most of them passed,but some of
>> the fs test and the syscall test failed,i will look into them soon
>> if you have interest,i can give you more detail results
>
> I've not used ltp, but if you do find anything useful I would be
>interested.
>
ok,i will let you know if something found
> Regards
> Chris
>
>--
>Algorithmics,The Fruit Farm,Ely Road,Chittering,CAMBS CB5 9PH,ENGLAND
>P: +44 1223 706200 F: +44 1223 706250 W: http://www.algor.co.uk
Regards
Zhang Fuxin
fxzhang@ict.ac.cn
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-12-05 15:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-12-05 13:53 Re: 2.4.16 for algorithmics p6032 Zhang Fuxin
-- strict thread matches above, loose matches on Subject: below --
2001-12-05 14:38 Zhang Fuxin
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.