About FCode driver
  Home FAQ Contact Sign in
comp.lang.forth.mac only
 
Advanced search
POPULAR GROUPS

more...

comp.lang.forth.mac Profile…
 Up
About FCode driver         


Author: roturier
Date: Aug 27, 2006 21:04

Hi there,

First of all, this messgae is cross-posted in both
comp.sys.mac.programmer.misc and comp.lang.forth.mac.

I am writing the FCode driver for some storage adapter
for PPC Mac. Some work has been done so far that Mac
OSX can install into the volume of the adapter. However,
after system reboots, the BUSY LED of the adapter flashs
for like 5 seconds(lots of data have been read) and system
just hangs. Apple logo is shown then but not the spinner,
and system fan starts full-speed running after a few
seconds. The adapter firmware side is checked; All issued
commands are completed normally, and they are all from
FCode driver, not any one from encapsulated runtime driver.

The kernel panic messages looks like this. (with boot-args
flag -v)
Show full article (1.95Kb)
3 Comments
Re: About FCode driver         


Author: Dennis Ruffer
Date: Aug 28, 2006 06:48

On 2006-08-28 00:04:24 -0400, roturier@gmail.com said:
> Hi there,
>
> First of all, this messgae is cross-posted in both
> comp.sys.mac.programmer.misc and comp.lang.forth.mac.
>
> I am writing the FCode driver for some storage adapter
> for PPC Mac. Some work has been done so far that Mac
> OSX can install into the volume of the adapter. However,
> after system reboots, the BUSY LED of the adapter flashs
> for like 5 seconds(lots of data have been read) and system
> just hangs. Apple logo is shown then but not the spinner,
> and system fan starts full-speed running after a few
> seconds. The adapter firmware side is checked; All issued
> commands are completed normally, and they are all from
> FCode driver, not any one from encapsulated runtime driver.
Show full article (2.95Kb)
2 Comments
Re: About FCode driver         


Author: roturier
Date: Aug 29, 2006 19:37

Dennis,

The problem *seems* to be kernel driver matching issue.
I may now let go the FCode driver part and try debugging
in runtime driver side.

Thanks a lot for your kindly help!

KC
1 Comment
Re: About FCode driver         


Author: Dennis Ruffer
Date: Aug 31, 2006 19:21

On 2006-08-29 22:37:25 -0400, roturier@gmail.com said:
> Dennis,
>
> The problem *seems* to be kernel driver matching issue.
> I may now let go the FCode driver part and try debugging
> in runtime driver side.
>
> Thanks a lot for your kindly help!
>
> KC

Glad I could be of some help. It does sound like you are on the correct track.

DaR
no comments