canonselphy: Delete docs since moved to selphyneo.
This commit is contained in:
parent
ccb5429fae
commit
6aff01fdd1
|
@ -1405,51 +1405,4 @@ struct dyesub_backend canonselphy_backend = {
|
||||||
0x41 if the 'Wide' paper tray is loaded with a 'P' ribbon. A '0' is used
|
0x41 if the 'Wide' paper tray is loaded with a 'P' ribbon. A '0' is used
|
||||||
to signify nothing being loaded.
|
to signify nothing being loaded.
|
||||||
|
|
||||||
***************************************************************************
|
|
||||||
Selphy CP820/CP910/CP1000/CP1200:
|
|
||||||
|
|
||||||
Radically different spool file format! 300dpi, same print sizes, but also
|
|
||||||
adding a 50x50mm sticker and 22x17.3mm ministickers, though I think the
|
|
||||||
driver treats all of those as 'C' sizes for printing purposes.
|
|
||||||
|
|
||||||
Printer does *not* require use of a spooler! Huzzah!
|
|
||||||
|
|
||||||
32-byte header:
|
|
||||||
|
|
||||||
0f 00 00 40 00 00 00 00 00 00 00 00 00 00 01 00
|
|
||||||
01 00 ?? 00 00 00 00 00 XX 04 00 00 WW ZZ 00 00
|
|
||||||
|
|
||||||
?? == 50 (P)
|
|
||||||
== 4c (L)
|
|
||||||
== 43 (C)
|
|
||||||
|
|
||||||
XX == e0 (P)
|
|
||||||
80 (L)
|
|
||||||
40 (C)
|
|
||||||
|
|
||||||
WW == 50 (P)
|
|
||||||
c0 (L)
|
|
||||||
9c (C)
|
|
||||||
|
|
||||||
ZZ == 07 (P)
|
|
||||||
05 (L)
|
|
||||||
02 (C)
|
|
||||||
|
|
||||||
P == 7008800 == 2336256 * 3 + 32 (1872*1248)
|
|
||||||
L == 5087264 == 1695744 * 3 + 32 (1536*1104)
|
|
||||||
C == 2180384 == 726784 * 3 + 32 (1088*668)
|
|
||||||
|
|
||||||
It is worth mentioning that the image payload is Y'CbCr rather than the
|
|
||||||
traditional YMC (or even BGR) of other dyseubs. Our best guess is that
|
|
||||||
we need to use the JPEG coefficients, although we realistically have
|
|
||||||
no way of confirming this.
|
|
||||||
|
|
||||||
It is hoped that the printers do support YMC data, but as of yet we
|
|
||||||
have no way of determining if this is possible.
|
|
||||||
|
|
||||||
Also, we have reports of the printer not quite behaving properly
|
|
||||||
in the face of multiple jobs; it's possible this thing may need a
|
|
||||||
backend after all, but more sniffs will need to be performed to determine
|
|
||||||
what the status readbacks (if any) mean.
|
|
||||||
|
|
||||||
*/
|
*/
|
||||||
|
|
Loading…
Reference in New Issue