Sarnath Kannan wrote:
sorry for jumping in between as i was out on long leave.
there is absoluetely no relation of bogus interrupts
with openpic_init is populating reserved memory areas of EPIC.
even i agree openpic_init is populating reserved memory areas of EPIC may
need a second thought.
you
Hi Ashish,
what I felt was, populating reserved areas
is a bug. Thats what I accentuated. Moreover
I has said that this could be a __possible__
cause for getting bogus interrupts. I would
say there is 80% possibility.
Moreover if u can read the EPIC manual,
u can notice that IVPR and SVPR both
In message 5BFFEE450E4C9264CB2CB0E906D67860 at j_padron.joseane.zzn.com you
wrote:
We have Metrowerks CodeWarrior (for Windows). It has a little application
and we use it to program the flash (via the Wigglers BDM): write and erase.
OK.
But now, we are starting with embedded linux and we
Sarnath Kannan wrote:
Hi Ashish,
what I felt was, populating reserved areas
is a bug.
It's only a bug if we don't know we are doing this and
it is causing problems. We know we can do what we
are doing without trouble. I'm not trying to
justify this hack or claim it is the proper
At 10:09 AM 11/12/01 +0100, Juan Padron wrote:
Hi:
I?m new in this list.
I have a beginner question.
We have Metrowerks CodeWarrior (for Windows). It has a little
application and we use it to program the flash (via the Wigglers BDM):
write and erase.
But now, we are starting with
I have no idea of hurting people. But if a bug
is pointed out, there is no harm in accepting it.
More importanly, you should do something constructive and fix it.
I thiught I did that, but noone seems to be interested.. ;-)
Dag
** Sent via the linuxppc-embedded mail list. See
Dag Nygren wrote:
I thiught I did that, but noone seems to be interested.. ;-)
Yeah :-). I was hoping Paul or someone else would make a suggestion.
A few of us (and people more interested and affected by OpenPIC other
than me) had discussed some other, slightly more pleasing hacks.
Right
Dan Malek wrote:
Sarnath Kannan wrote:
hi all,
The Sandpoint user's manual says that WinBond's IDE controller is disabled
in mode 1 (s3-down, s4-up), but MontaVista's kernel works in mode 1 with
IDE support!
How is this possible ?
Because the documentation is misleading...
The
