On Saturday 20 October 2007 19:11:56 Sergei Shtylyov wrote:
What I don't like is that both PIIX4 and PCI-648 are sharing IRQ15
(PIIX4 is in legacy mode, so it uses edge-triggered IRQ15 which is not
shareable). You don't have drives connected to PIIX4, do you? However, it
doesn't look like
Hello.
Martin Rogge wrote:
00:04.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
(prog-if 80 [Master])
Flags: medium devsel
[virtual] Memory at 01f0 (32-bit, non-prefetchable) [disabled]
[size=8]
[virtual] Memory at 03f0 (type 3,
Martin Rogge wrote:
00:04.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
(prog-if 80 [Master])
Flags: medium devsel
[virtual] Memory at 01f0 (32-bit, non-prefetchable) [disabled]
[size=8]
[virtual] Memory at 03f0 (type 3, non-prefetchable)
On Friday 19 October 2007 22:26:23 Sergei Shtylyov wrote:
Hello.
Martin Rogge wrote:
BTW, can you try adding #define DEBUG to the driver meanwhile?..
Yoda said: Try not. Do or do not. There is no try.
:-)
So I did it. To be precise, I #defined both DEBUG and CMD_DEBUG.
Hello.
Martin Rogge wrote:
BTW, can you try adding #define DEBUG to the driver meanwhile?..
Yoda said: Try not. Do or do not. There is no try.
:-)
So I did it. To be precise, I #defined both DEBUG and CMD_DEBUG. However, I am
not sure the result is conclusive.
On a good kernel
On Wednesday 17 October 2007 22:40:21 Sergei Shtylyov wrote:
BTW, can you try adding #define DEBUG to the driver meanwhile?..
Yoda said: Try not. Do or do not. There is no try.
So I did it. To be precise, I #defined both DEBUG and CMD_DEBUG. However, I am
not sure the result is conclusive.
On Wednesday 17 October 2007 00:14:26 Bartlomiej Zolnierkiewicz wrote:
Martin, could you run git-bisect (http://kerneltrap.org/node/11753 - sorry
for not explaining the procudure myself but Linus did it really well)
starting with:
git bisect good
Hello.
Martin Rogge wrote:
Martin, could you run git-bisect (http://kerneltrap.org/node/11753 - sorry
for not explaining the procudure myself but Linus did it really well)
starting with:
git bisect good 688a87d145e04f6761c63e7f2e19fd9b3e4ca060
git bisect bad
Martin Rogge wrote:
Could you git-bisect this?
Although I have a couple of patch suspects (dealing with interrupts),
all worked fine with PCI-649 just fine. PCI-648 is not really much
different from 649 according to specs...
Yes, I found the same when I managed to send the CMD 648 into
Sergei Shtylyov wrote:
Martin Rogge wrote:
Could you git-bisect this?
Although I have a couple of patch suspects (dealing with interrupts),
all worked fine with PCI-649 just fine. PCI-648 is not really much
different from 649 according to specs...
Yes, I found the same when I managed
Hello.
Mark Lord wrote:
Could you git-bisect this?
Although I have a couple of patch suspects (dealing with
interrupts),
all worked fine with PCI-649 just fine. PCI-648 is not really much
different from 649 according to specs...
Yes, I found the same when I managed to send the CMD
Hi,
On Tuesday 16 October 2007, Mark Lord wrote:
Sergei Shtylyov wrote:
Martin Rogge wrote:
Could you git-bisect this?
Although I have a couple of patch suspects (dealing with interrupts),
all worked fine with PCI-649 just fine. PCI-648 is not really much
different from 649
Martin Rogge wrote:
Hi Sergei and Bartlomiej,
I have read in the changelog that both of you got linux kernel patches into
2.6.22-rc1 for the cmd64x driver. I found that some patches introduced in
2.6.22-rc1 break the CMD648 operation of one of my machines. (Actually I
discovered it in
13 matches
Mail list logo
