Re: QSIC update and request

On 1/2/18 15:38, Toby Thain via cctalk wrote: > Err.. could be my mistake... I meant wherever you posted your last > technical note about QBus quirks. (I didn't look up the reference) Oh, that paper I wrote about how bus arbitration works on the Unibus and QBUS.  I'd thought of it as just a way

Re: QSIC update and request

On 2018-01-02 3:00 PM, David Bridgham via cctalk wrote: > On 01/02/2018 02:05 PM, Toby Thain via cctalk wrote: > >>> Oh, I hadn't thought of Toby possibly meaning that.  Yeah, I'm unlikely >>> to write up much documentation on the internals of the QSIC for people >>> who want to add other

Re: QSIC update and request

On 01/02/2018 02:05 PM, Toby Thain via cctalk wrote: >> Oh, I hadn't thought of Toby possibly meaning that.  Yeah, I'm unlikely >> to write up much documentation on the internals of the QSIC for people >> who want to add other devices.  However, not only will the source be > Yes, that's what I

Re: QSIC update and request

On 2018-01-02 1:17 PM, David Bridgham via cctalk wrote: > On 01/02/2018 01:13 PM, Noel Chiappa via cctalk wrote: > > >> If you mean the 'software' for additional controllers - that would be a _lot_ >> harder (plus to which it's an entirely different tool-chain, yadda-yadda). >> 'Use the source,

Re: QSIC update and request

On 01/02/2018 01:13 PM, Noel Chiappa via cctalk wrote: > If you mean the 'software' for additional controllers - that would be a _lot_ > harder (plus to which it's an entirely different tool-chain, yadda-yadda). > 'Use the source, Luke!', I'm probably afraid... Oh, I hadn't thought of Toby

Re: QSIC update and request

> From: Toby Thain > If the documentation is good enough, people in the community will be > able to provide the software. You mean, host drivers? Yeah, that documentation will be pretty trivial: 'there's this extra register, just like the one in the RLV12; the top 6 bits of the DMA

Re: QSIC update and request

On 01/02/2018 12:45 PM, Toby Thain via cctalk wrote: > If the documentation is good enough, people in the community will be > able to provide the software. The quick answer is that it's pretty simple.  We take the cylinder/head/sector addresses and consider them a Linear Block Address.  Then we

Re: QSIC update and request

On 2018-01-02 9:01 AM, Noel Chiappa via cctalk wrote: > > From: Mark J. Blair > > > I wonder if it might also be useful in any of the QBUS MicroVAXen? > > Hardwarewise, it should be fine. Softwarewise... well... > ... > Anyway, you can see where this is going. For people who can tweak

Re: QSIC update and request

> From: Mark J. Blair > I wonder if it might also be useful in any of the QBUS MicroVAXen? Hardwarewise, it should be fine. Softwarewise... well... The issue is that we're currently only planning to emulate the RK11 and RP11, because we're not up for the hassle involved in emulating

Re: QSIC update and request

This looks pretty interesting! I think I've managed to miss previous discussion of it. I wonder if it might also be useful in any of the QBUS MicroVAXen? -- Mark J. Blair, NF6X http://www.nf6x.net/

Re: QSIC update and request

> From: David Bridgham > I could ask for a lot more really but that's pretty good. IMO we're 'over the hump' on the prototype phase of the project. The complete QBUS interface (including DMA and interrupts) are done, and very thoroughly tested, and now we have the SD interface up and

QSIC update and request

Even though I've been quiet, I have been making slow progress on the QSIC in the background.  For those who've forgotten what the QSIC project is about, here's the description: http://pdp10.froghouse.org/qsic/html/overview.html We've been working away on getting communications with the SD card