Welcome, Guest. Please login or register.

Author Topic: newb questions, hit the hardware or not?  (Read 63601 times)

Description:

0 Members and 4 Guests are viewing this topic.

Offline DamageXTopic starter

  • Sr. Member
  • ****
  • Join Date: Jun 2005
  • Posts: 339
    • Show all replies
    • http://www.hyakushiki.net/
newb questions, hit the hardware or not?
« on: January 09, 2006, 07:03:48 AM »
I want to write some programs in assembly (please don't suggest a HLL as I won't use one) on my A2000. I want to do file I/O, some graphics on a HAM6 screen, and perhaps audio as well. Now the question is how to go about it. Looking at bits of source code and documentation that I've been able to find, the method of disabling the OS and accessing hardware registers directly seems to be very clear. But, can OS calls still be used for file I/O in this case? And where could I learn to open a custom screen and play audio the OS-friendly way anyways?
 

Offline DamageXTopic starter

  • Sr. Member
  • ****
  • Join Date: Jun 2005
  • Posts: 339
    • Show all replies
    • http://www.hyakushiki.net/
Re: newb questions, hit the hardware or not?
« Reply #1 on: January 10, 2006, 01:45:07 AM »
This is just the kind of info I needed, thanks ^_^
 

Offline DamageXTopic starter

  • Sr. Member
  • ****
  • Join Date: Jun 2005
  • Posts: 339
    • Show all replies
    • http://www.hyakushiki.net/
Re: newb questions, hit the hardware or not?
« Reply #2 on: July 14, 2014, 08:22:40 AM »
for the record...
Code: [Select]
.nosignal:
move.l _WBenchMsg(pc),d0
beq.s .notwb
move.l a0,a1
jsr _LVOForbid(a6)
jsr _LVOReplyMsg(a6)

.notwb:
move.l d7,d0
rts

I was informed that this part is buggy. a0 was perhaps a typo for d0, and it is also not clear if a1 is preserved during the call to LVOForbid
 

Offline DamageXTopic starter

  • Sr. Member
  • ****
  • Join Date: Jun 2005
  • Posts: 339
    • Show all replies
    • http://www.hyakushiki.net/
Re: newb questions, hit the hardware or not?
« Reply #3 on: July 20, 2014, 08:25:38 AM »
Thanks for jacking my thread, LOL.