Re: Royal Navy adopts W2000 for nuclear defense (or the navy lark part 2)
From: John Larkin (jjlarkin_at_highlandSNIPtechTHISnologyPLEASE.com)
Date: 10/16/04
- Next message: John Larkin: "Re: If Kerry is elected..."
- Previous message: Ganesh Okade: "Re: PDIUSBD12 returns Buffer Overrun"
- In reply to: robin.pain_at_tesco.net: "Re: Royal Navy adopts W2000 for nuclear defense (or the navy lark part 2)"
- Next in thread: Rich Grise: "Re: Royal Navy adopts W2000 for nuclear defense (or the navy lark part 2)"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 16 Oct 2004 08:37:37 -0700
On 16 Oct 2004 04:18:05 -0700, robin.pain@tesco.net
(robin.pain@tesco.net) wrote:
>John Larkin <jjlarkin@highlandSNIPtechTHISnologyPLEASE.com> wrote in message news:<t1qvm095fevnt365vuc4m6inlie9jbreuh@4ax.com>...
>> On 15 Oct 2004 01:12:23 -0700, robin.pain@tesco.net
>> (robin.pain@tesco.net) wrote:
>>
>> >"Pat Ford" <pat.ford@nrc.ca> wrote in message news:<ckloc5$dtl$1@nrc-news.nrc.ca>...
>> >> <robin.pain@tesco.net> wrote in message
>> >> news:bd24a397.0410132318.7aa5fbff@posting.google.com...
>> >> > "Pat Ford" <pat.ford@nrc.ca> wrote in message
>> news:<ckj2m6$ru0$1@nrc-news.nrc.ca>...
>> >> > > >
>> >> > > > If I press <escape> to abort the start-up memory test, then the result
>> >> > > > is always the same i.e.
>> >> > > >
>> >> > > > 2^n bytes OK
>> >> > > >
>> >> > > > ...you see! They have no pride, no one cares, it's just a job for
>> >> > > > getting money. That's why it will always be ugly and unreliable.
>> >> > > >
>> >> > > > Cheers
>> >> > > > Robin
>> >> > >
>> >> > > That happens before the OS is loaded, that is BIOS not M$.
>> >> > >
>> >> > > Pat
>> >> >
>> >> > I agree, M$ do not have full control of the operating system.
>> >> >
>> >> > Cheers
>> >> > Robin
>> >>
>> >> M$ is the operating system! The bios is below that, M$ has it's problems
>> >> ( I'm a unix type) but this example isn't one of them.
>> >
>> >Oh, I thought the BIOS was integral. Who else uses it then? (obviously
>> >UNIX don't because you would have said so) :)
>> >
>>
>> I use the bios to boot IBM's Dos2000. Works fine.
>>
>> >This is the rub: If you make something beautiful on the outside then
>> >it is more likely beautiful inside. M$ don't give a damn e.g. the Caps
>> >lock key, a useless thing is made larger and inserted between two
>> >(three) of the most often used keys.
>>
>> Caps lock is indispensable, as real programmers code in uppercase.
>>
>> John
>
>Ah yes, make big goof about BIOS - so I learn something - thanks to
>all, presumably there is a spec somewhere for BIOS and anyone can
>write there own "OS" to connect with it, even something incredibly
>trivial because it would be so much cheaper than making your own
>controller from scratch?
>
>UPPER CASE verses lower case:-
>If you want to provide the maximum meaning for the minimum effort ya
>gotta have as much variety as possible. The same thing applies to
>prose as well as code so lower case is not a stylistic thing, it is a
>better thing:-
>
>
>LDX INPUT //INPUT IS A CONSTANT
>STX INPUT_CACHE
>
>
>ldaa INPUT //no comment necessary
>staa input //no qualification necessary
>
>
>Which example is easier for the brain to decode and contains more
>information in less text?
>
>Cheers
>Robin
6803 code? Wow, I did a lot of that. I actually wrote an RTOS for the
6800 once, which was a nuisance because the stack operations were even
more limited than for the 6803.
Is less text good?
But I comment every line. Here's some 68K code. The formatting may get
messed up by the newsgroup stuff, but it looks real nice on paper.
.SBTTL . LMAX : LOAD A MAXIM SERIAL DAC
; WE SHIFT 16 BITS INTO A MAXIM DAC, MSB FIRST. FOR THE SINGLE
; 16-BIT MAX5205, THIS IS JUST DATA. FOR THE QUAD-12 MAX5742,
; OUR INPUT IS 4 COMMAND BITS FOLLOWED BY 12 DATA BITS.
; D0 IS BOARD SUBADDRESS
; D2 IS SLOT NUMBER
; D4 IS 16-BIT DAC CMD+DATA (FOR QUAD-12) OR DATA (FOR 16)
; D7 IS LOOP COUNTER
; A5 USED AS BAWD LATCH POINTER
; CARDCAGE D0 IS SERIAL DATA
; D1 IS CLOCK, ALWAYS RISING EDGE, COURTESY PEELS.
LMAX: MOVEA.W # BAWD, A5 ; AIM AT BUS WRITE DATA LATCH
CLR.B (A5) ; ZAP THE DATA LATCH
MOVE.B D0, BADD.W ; SET 'A' LINES AND ENABLE WRITE DRIVER
MOVE.B D2, PORTD.W ; DO THE SLOT SELECT
MOVE.L # 16-1, D7 ; PREPARE TO DO 16 BITS
L280: LSL.W # 1, D4 ; TEST MS BIT OF DACDATA
BCS.S L281 ; SKIP FOR A '1'
CLR.B (A5) ; SHIFT A 0 : DATA LOW, CLOCK LOW
MOVE.B # B1, (A5) ; DATA LOW, CLOCK HIGH
DBF D7, L280 ; AND LOOP
BRA.S L289
L281: MOVE.B # B0, (A5) ; SHIFT A 1 : DATA HIGH, CLOCK LOW
MOVE.B # B1+B0, (A5) ; DATA HIGH, CLOCK HIGH
DBF D7, L280
L289: CLR.B (A5) ; FINALLY DROP CLOCK
MOVE.B # 0Fh, PORTD.W ; DESELECT THIS SLOT,
MOVE.B # B7, BADD.W ; KILL 'A' LINES, AND ZAP WRITESTUFF
RTS
The .SBTTL directive creates an entry in the program table of
contents, which appears first in the listing, with page and line
number appended.
John
- Next message: John Larkin: "Re: If Kerry is elected..."
- Previous message: Ganesh Okade: "Re: PDIUSBD12 returns Buffer Overrun"
- In reply to: robin.pain_at_tesco.net: "Re: Royal Navy adopts W2000 for nuclear defense (or the navy lark part 2)"
- Next in thread: Rich Grise: "Re: Royal Navy adopts W2000 for nuclear defense (or the navy lark part 2)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
